From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Theodore Tso <tytso@mit.edu>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
tomas.winkler@intel.com
Subject: Re: iwl4965 and driver merging policy
Date: Fri, 28 Sep 2007 13:07:39 +1000 [thread overview]
Message-ID: <1190948859.6158.62.camel@pasglop> (raw)
In-Reply-To: <20070928024759.GG8688@thunk.org>
>
> Well, pulling in iwlwifi would require also pulling in the mac80211
> subsystem, so it's not quite that simple (although I'm not sure what's
> holding back that going into the kernel.)
I though that was already in 2.6.23 ... my bad if I missed something
(there is definitely something there called net/mac80211)
> I had no problem building my personal production kernel by taking
> 2.6.23-rc8, and doing a git pull from the everything branch in John
> Linville's wireless-dev git tree. It's probably too late to pull it
> for 2.6.23-rc8 (although if Linux wanted to do it it's only one git
> pull command away :-), but it would be really nice if it could get
> merged in for 2.6.24.
Yes, I agree -rc8 seems to be a tad too late, I'm just surprised we
didn't get it in earlier though since it seems it's been around and
useable for some time.
Cheers,
Ben.
next prev parent reply other threads:[~2007-09-28 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 1:39 iwl4965 and driver merging policy Benjamin Herrenschmidt
2007-09-28 2:30 ` John W. Linville
2007-09-28 3:15 ` Benjamin Herrenschmidt
2007-09-28 13:28 ` John W. Linville
2007-09-28 2:47 ` Theodore Tso
2007-09-28 3:07 ` Benjamin Herrenschmidt [this message]
2007-10-01 8:24 ` Jiri Kosina
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=1190948859.6158.62.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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