From: William Lee Irwin III <wli@holomorphy.com>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [0/7] LEON SPARC V8 processor support for linux-2.6.10
Date: Tue, 4 Jan 2005 11:21:57 -0800 [thread overview]
Message-ID: <20050104192157.GO2708@holomorphy.com> (raw)
In-Reply-To: <41DAE87B.8030405@gaisler.com>
On Tue, Jan 04, 2005 at 08:03:23PM +0100, Jiri Gaisler wrote:
> I am not sure that the pathes for serial and ethernet drivers
> should be sent to the sparclinux list. If not, please advise on
> where I should submit them.
Jeff Garzik and netdev@oss.sgi.com generally handle network drivers.
Russell King and linux-kernel@vger.kernel.org probably handle
serial drivers considered for inclusion.
I don't have a particularly organized or sophisticated plan for a
staged merging of the drivers. If either should care to absorb the
drivers instead of merely acking them, it's just as well. Both will
generally see anything going across linux-kernel.
-- wli
prev parent reply other threads:[~2005-01-04 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 19:03 [0/7] LEON SPARC V8 processor support for linux-2.6.10 Jiri Gaisler
2005-01-04 19:21 ` William Lee Irwin III [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=20050104192157.GO2708@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jiri@gaisler.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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