linux-kernel - Re: [PATCH 1/2] misc: remove CONFIG_MISC

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: <2282172.TF7nejTDIZ@wuerfel>
Date:	Mon, 19 Sep 2011 10:47:50 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Greg KH <greg@...ah.com>, Jean Delvare <khali@...ux-fr.org>,
	Luciano Coelho <coelho@...com>, matti.j.aaltonen@...ia.com,
	johannes@...solutions.net, linux-kernel@...r.kernel.org,
	sameo@...ux.intel.com, mchehab@...radead.org,
	linux-media@...r.kernel.org, linux-omap@...r.kernel.org,
	Tony Lindgren <tony@...mide.com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 1/2] misc: remove CONFIG_MISC_DEVICES

On Sunday 18 September 2011 11:45:16 Randy Dunlap wrote:
> >> We have fallbacks to Andrew and/or GregKH currently, but GregKH is not
> >> consistent or timely with applying drivers/misc/ patches.  It deserves better.
> >> [added him to Cc: list]
> > 
> > I do try to handle patches sent to me for misc/ in time for the
> > different merge windows as that directory contains drivers that have
> > moved out of the staging/ directory.
> > 
> > But yes, I'm not the overall drivers/misc/ maintainer, do we really need
> > one?  If so, I can easily start maintaining a development tree for it to
> > keep it separate for the different driver authors to send me stuff and
> > start tracking it more "for real" if Arnd doesn't want to do it.
> 
> We need for the patches to be applied in a timely manner.
> Sometimes when there is no real maintainer, that does not happen.

I think the other equally import aspect of maintainership that
drivers/misc (and drivers/char) needs is someone who says no to
stuff that doesn't belong there and helps submitters to find a
proper place where appropriate and to come up with a proper user
interface abstraction.

I'm definitely willing to do that part.

Greg, how about we both formally take ownership of driver/{misc,char}
and you track the patches while I do the bulk of the reviews? You
are definitely better than me with the patch tracking workflow.

	Arnd
--
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/