From: Bill Gatliff <bgat@billgatliff•com>
To: linuxppc-dev@ozlabs•org, lm-sensors@lm-sensors•org
Subject: Re: [PATCH 0/2] *** SUBJECT HERE ***
Date: Tue, 05 Jan 2010 22:32:16 -0600 [thread overview]
Message-ID: <4B441250.3090307@billgatliff.com> (raw)
In-Reply-To: <1262752236-1937-2-git-send-email-bgat@billgatliff.com>
Bill Gatliff wrote:
> *** BLURB HERE ***
>
Dangit, sometimes I really hate it when emacs leaves its backup files
around... :(
Like now, for example. Please disregard the noise generated by my
careless use of filename wildcards...
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat@billgatliff•com
next prev parent reply other threads:[~2010-01-06 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 4:30 [RFC/PATCH 0/2] Updates to improve device tree support Bill Gatliff
2010-01-06 4:30 ` [PATCH 0/2] *** SUBJECT HERE *** Bill Gatliff
2010-01-06 4:30 ` [PATCH 1/2] Use struct of_i2c_gpio_chip instead of raw struct gpio_chip Bill Gatliff
2010-01-06 4:30 ` [PATCH 2/2] Reorder initialization to better support device tree data Bill Gatliff
2010-01-06 4:32 ` Bill Gatliff [this message]
2010-01-07 8:55 ` [lm-sensors] [RFC/PATCH 0/2] Updates to improve device tree support Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B441250.3090307@billgatliff.com \
--to=bgat@billgatliff$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=lm-sensors@lm-sensors$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox