public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	tomas.winkler@intel.com
Subject: iwl4965 and driver merging policy
Date: Fri, 28 Sep 2007 11:39:27 +1000	[thread overview]
Message-ID: <1190943567.6158.50.camel@pasglop> (raw)

Hi !

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 ? :-)

Cheers,
Ben.



             reply	other threads:[~2007-09-28  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  1:39 Benjamin Herrenschmidt [this message]
2007-09-28  2:30 ` iwl4965 and driver merging policy 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
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=1190943567.6158.50.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 \
    /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