netdev - Re: Moving drivers into staging (was Re: [GIT PULL] SCSI fixes for 2.6.32-rc3)

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] [day] [month] [year] [list]

Message-ID: <20091015060303.GA32415@elte.hu>
Date:	Thu, 15 Oct 2009 08:03:03 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Joe Perches <joe@...ches.com>, Greg KH <gregkh@...e.de>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	James Bottomley <James.Bottomley@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jing Huang <huangj@...cade.com>, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org
Subject: Re: Moving drivers into staging (was Re: [GIT PULL] SCSI fixes for
	2.6.32-rc3)


* Stefan Richter <stefanr@...6.in-berlin.de> wrote:

> > Well, the answer is obvious i think. Tell me, at a glance, if you 
> > see a patch on lkml, which one is for a staging driver to be 
> > obsoleted, and which one is the one going upstream real soon? The 
> > patches say:
> > 
> >  +++ a/drivers/staging/foo/x.c
> > 
> >  +++ a/drivers/staging/bar/y.c
> > 
> > Then tell me the same at a glance if you see patches for:
> > 
> >  +++ a/drivers/staging/wip/x.c
> > 
> >  +++ a/drivers/staging/bad/y.c
> 
> Does this information matter much?

Yes. You might not appreciate it as you are active in a relatively 
narrow field (so all patches in your world have an 'obvious' place) - 
but i for example take most of the context of a change from the email 
itself and the more self-descriptive it is, the better. I would be more 
likely to review work-in-progress patches while not bother about 
obsolete drivers on the way out. YMMV.

> What's more interesting is whether development activity will _lead_ to 
> a driver being moved from bad or ugly to good.

... a prerequisite of which is for more developers to be accutely aware 
of in what state a driver is.

Anyway ... it's all up to Greg and he indicated that he wants the 
simplest structure, which is fair enough.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html