linux-kernel - Re: [PATCH 1/4] strip: move driver to staging

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Oct 2009 12:46:45 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [PATCH 1/4] strip: move driver to staging

On Tue, Oct 20, 2009 at 09:06:27AM -0700, Randy Dunlap wrote:
> On Tue, 20 Oct 2009 14:17:07 +0900 John W. Linville wrote:
> 
> > Move the strip ("Starmode Radio IP") driver to drivers/staging.  For
> > several years this driver has only seen API "bombing-run" changes, and
> > few people ever had the hardware.  This driver represents unnecessary
> > ongoing maintenance for no clear benefit.
> > 
> > This patch brought to you by the "hacking" session at the 2009 Kernel
> > Summit in Tokyo, Japan...
> 
> is drivers/staging/ a temporary home or a permanent home?

I would presume it to be "permanent until removed"...

> so no explanation of what it means to be in drivers/staging/ and
> no warning to users?  either in Kconfig or in feature-removal-schedule.txt?

Moving it to staging _is_ the warning.  As for the removal schedule,
I imagined that Greg would "do the needful" before actually removing
the driver.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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/