From: Adrian Cox <adrian@humboldt.co.uk>
To: Greg KH <greg@kroah.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>,
lm78@Stimpy.netroedge.com
Subject: Re: MPC10x I2C driver update
Date: 01 Oct 2003 09:43:59 +0100 [thread overview]
Message-ID: <1064997842.18737.676.camel@newt> (raw)
In-Reply-To: <20030930204716.GA20450@kroah.com>
On Tue, 2003-09-30 at 21:47, Greg KH wrote:
> On Tue, Sep 30, 2003 at 10:43:55AM +0100, Adrian Cox wrote:
> > I'd like to get this into the kernel. Which would be more useful to
> > people:
> > 1) Getting it into lm-sensors?
> > 2) Getting it into linuxppc-2.4-devel?
>
> 3) sending me a patch to get it into the 2.6 kernel tree.
Once I can boot 2.6 on one of my MPC107 boards, I'll update the patch.
- Adrian Cox
http://www.humboldt.co.uk/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-10-01 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 9:43 MPC10x I2C driver update Adrian Cox
2003-09-30 20:47 ` Greg KH
2003-10-01 8:43 ` Adrian Cox [this message]
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=1064997842.18737.676.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=greg@kroah.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=lm78@Stimpy.netroedge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).