Home » Mailing list archives » linux-kernel » 2007 » September » 27

iwl4965 and driver merging policy

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Benjamin Herrenschmidt <benh@...>
To: John W. Linville <linville@...>
Cc: Linus Torvalds <torvalds@...>, Andrew Morton <akpm@...>, Linux Kernel list <linux-kernel@...>, <tomas.winkler@...>
Subject: iwl4965 and driver merging policy
Date: Thursday, September 27, 2007 - 9:39 pm

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.


-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
iwl4965 and driver merging policy, Benjamin Herrenschmidt, (Thu Sep 27, 9:39 pm)
Re: iwl4965 and driver merging policy, John W. Linville, (Thu Sep 27, 10:30 pm)
Re: iwl4965 and driver merging policy, Benjamin Herrenschmidt, (Thu Sep 27, 11:15 pm)
Re: iwl4965 and driver merging policy, John W. Linville, (Fri Sep 28, 9:28 am)
Re: iwl4965 and driver merging policy, Theodore Tso, (Thu Sep 27, 10:47 pm)
Re: iwl4965 and driver merging policy, Jiri Kosina, (Mon Oct 1, 4:24 am)
Re: iwl4965 and driver merging policy, Benjamin Herrenschmidt, (Thu Sep 27, 11:07 pm)