lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 21:23:35 -0700 (PDT)
From:	david@...g.hm
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Ingo Molnar <mingo@...e.hu>, Greg KH <gregkh@...e.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: removing existing working drivers via staging

for those who were reading this thread, the topic has come up again in the 
thread titled

[PATCH 1/4] strip: move driver to staging

where a driver is being moved to staging because it does not have a 
maintainer and the only changes to it for some time have been due to 
kernel API changes.

the maintainer of the area feels that it's too much work to allow the 
driver to remain because it must be updated when kernel APIs change.


this is exactly the 'wants to get rid of' category I mentioned being 
concerned about below.


I don't know what was decided at the kernel summit where this was 
discussed, how easy is it supposed to be to drop drivers out of the 
kernel?

David Lang

On Thu, 15 Oct 2009, david@...g.hm wrote:

> Date: Thu, 15 Oct 2009 12:57:49 -0700 (PDT)
> From: david@...g.hm
> To: Stefan Richter <stefanr@...6.in-berlin.de>
> Cc: Ingo Molnar <mingo@...e.hu>, Greg KH <gregkh@...e.de>,
>     Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
>     linux-kernel <linux-kernel@...r.kernel.org>
> Subject: Re: removing existing working drivers via staging
> 
> On Thu, 15 Oct 2009, Stefan Richter wrote:
>
>> david@...g.hm wrote:
>>> it's these users who will discover the missing driver and care about it,
>>> not the distros.
>> 
>> I think we are talking about stuff of which users will typically
>> discover that it plainly doesn't work long before it vanishes from any
>> kernel distribution, or of which there is a superior alternative already
>> available.
>
> if there's a superior alternative already available staging isn't needed 
> (like the e1000 split), but I have also seen many new systems added to the 
> kernel that the author thinks covers all the old ones, only to find out when 
> people get it in the real world that it doesn't cover all existing hardware. 
> but this is an existing problem that is already being handled.
>
>
>
> if it clearly doesn't work that is also fine with me.
>
> however, that is not the criteria that has been expressed.
>
> from earlier in this thread
>
>        - For drivers currently in the kernel tree, that the subsystem
>          maintainer, for whatever reason, feels is obsolete / broken /
>          needs major cleaning / wants to get rid of, can be submitted
>          to the staging maintainer to be moved to the drivers/staging/
>          directory.
>
> it's the 'needs major cleaning' and 'wants to get rid of' portions that 
> concern me the most.
>
> 'obsolete' can mean that there is a superior alternative available, or it 
> could mean that the hardware the driver supports has not been manufactured in 
> several years (or, depending who you ask, several weeks ;-)
>
> David Lang
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists