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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20091026193604.GB23783@suse.de>
Date:	Mon, 26 Oct 2009 12:36:04 -0700
From:	Greg KH <gregkh@...e.de>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Joe Perches <joe@...ches.com>, Pavel Machek <pavel@....cz>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] strip: move driver to staging

On Mon, Oct 26, 2009 at 03:20:26PM -0400, John W. Linville wrote:
> On Mon, Oct 26, 2009 at 12:07:43PM -0700, Joe Perches wrote:
> > On Mon, 2009-10-26 at 11:48 -0700, Greg KH wrote:
> > > On Mon, Oct 26, 2009 at 06:24:34PM +0100, Pavel Machek wrote:
> > > > Anyway, for moving to staging, TODO file describing what needs to be
> > > > fixed before it is brought back was listed as a requirement.
> > > 	- A maintainer is needed to take ownership of this driver and
> > > 	  they must be willing to maintain and test any future api
> > > 	  changes needed.
> > 
> > There are a lot of files in the tree without assigned maintainers.
> > (want a list? ;)
> > 
> > I think adding a requirement that files have maintainers before
> > being added to not-staging is not a good thing.
> 
> This is not a blanket policy.  Please don't imply that it is.
> 
> > It is likely that strip could have be deleted without anyone caring.
> 
> Perhaps so...how would that be better?  It would be less work for Greg,
> but he seems to be fine with this...

Exactly, why are people who are not doing any work with these devices,
suddenly worried about any additional work for me?  As if people care
about my patch workload suddenly :)

As everyone here has no problem with this specific driver, or the other
ones posted, why is there even any discussion?

thanks,

greg k-h
--
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/