From: Jeff Garzik <jgarzik@pobox.com>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Netdev <netdev@oss.sgi.com>
Subject: Re: Steps for netdev-2.6 inclusion?
Date: Tue, 21 Dec 2004 15:03:15 -0500 [thread overview]
Message-ID: <41C88183.3020906@pobox.com> (raw)
In-Reply-To: <41AE7143.80505@linux.intel.com>
James Ketrenos wrote:
>
> Ok, its been a long time coming, but it appears the ipw* wireless
> drivers are to the point where being more proactive at getting them into
> the kernel is appropriate (at least based on the frequency of emails I'm
> getting of 'why isn't this in mainline?')
>
> So, what would be the set of steps required to get a version in the
> queue for inclusion?
Any updates? Where do we stand with this?
I would suggest sending a patch for each driver, diff'd against -mm
(which auto-includes my netdev-2.6 and wireless-2.6 queues).
Jeff
next prev parent reply other threads:[~2004-12-21 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 1:34 Steps for netdev-2.6 inclusion? James Ketrenos
2004-12-02 6:18 ` Jeff Garzik
2004-12-02 20:11 ` James Ketrenos
2004-12-03 10:33 ` Christoph Hellwig
2004-12-21 20:03 ` Jeff Garzik [this message]
2005-01-06 16:10 ` James Ketrenos
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=41C88183.3020906@pobox.com \
--to=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=netdev@oss.sgi.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).