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: Thu, 02 Dec 2004 01:18:32 -0500 [thread overview]
Message-ID: <41AEB3B8.2000406@pobox.com> (raw)
In-Reply-To: <41AE7143.80505@linux.intel.com>
It's fairly easy, just email me and netdev the patch for inclusion, and
it'll get reviewed.
Once review issues are addressed, I'll merge it immediately, which
causes it to be automatically propagated to Andrew Morton's -mm tree for
testing.
Once consensus agrees that we can push this + HostAP upstream, that's an
easy 10-minute task.
One potential showstopper is firmware crapola: I'm concerned about a
situation where we have drivers in the kernel, but the firmware must be
downloaded from SourceForge or somesuch. IOW, the kernel driver as-is
is useless without a differently-licensed firmware.
Comments?
Jeff
next prev parent reply other threads:[~2004-12-02 6:18 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 [this message]
2004-12-02 20:11 ` James Ketrenos
2004-12-03 10:33 ` Christoph Hellwig
2004-12-21 20:03 ` Jeff Garzik
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=41AEB3B8.2000406@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).