All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Thu, 27 Sep 2007 22:47:59 -0400	[thread overview]
Message-ID: <20070928024759.GG8688@thunk.org> (raw)
In-Reply-To: <1190943567.6158.50.camel@pasglop>

On Fri, Sep 28, 2007 at 11:39:27AM +1000, Benjamin Herrenschmidt wrote:
> 
> Just a little question in the light of the discussion we had at Kernel
> Summit about merging drivers upstream (and here, I strongly agree with
> Linus, hence my message).
> 
> I just got that new T61 laptop which happens to have an iwl4xxx chip.
> The distro I installed on it (ubuntu) has a driver for it. I suspect
> others do too and most users get it from some random external tree and
> use it.
> 
> Thus my question, why are we about to release 2.6.23 without it ?
> 
> It doesn't seem to pull any depedency nor affect any other external
> piece of code unless I'm missing something, so it's a perfect example of
> what we've been discussing back then: there is just no point not merging
> it at any time right ? :-)

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 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.

						- Ted

  parent reply	other threads:[~2007-09-28  2:48 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 [this message]
2007-09-28  3:07   ` Benjamin Herrenschmidt
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=20070928024759.GG8688@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomas.winkler@intel.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.