linux-kernel - Re: [PATCH v2 0/7] Driver core and sysfs changes for attribute groups

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]

Date:	Sun, 14 Jul 2013 11:32:06 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, oliver+list@...inagl.nl,
	khali@...ux-fr.org
Subject: Re: [PATCH v2 0/7] Driver core and sysfs changes for attribute groups

On Sun, Jul 14, 2013 at 10:32:58AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Jul 14, 2013 at 10:27:03AM -0700, Guenter Roeck wrote:
> > On Wed, Jul 10, 2013 at 05:35:58PM -0700, Greg Kroah-Hartman wrote:
> > > Hi all,
> > > 
> > > Here's the second iteration of the patchset to add better attribute
> > > group support to the driver core and sysfs.
> > > 
> > > I've tested these (shocker!) and everything works fine with them (I'm
> > > sending this from Linus's latest kernel with these 7 on top of it.)
> > > 
> > > I'd like to send these to Linus for 3.11 unless someone objects.
> > > 
> > Hi Greg,
> > 
> > I have not seen the series in the upstream kernel. Do you have an updated
> > plan to get it upstream ?
> > 
> > If needed I can carry the patches I need in my branch for now, so it doesn't
> > matter too much if the code misses 3.11. Still, it would help to know the
> > plan going forward.
> 
> I was planning on doing one more respin of the patches on Monday, and
> then getting them into 3.11-rc2 if possible so that everyone can start
> taking advantage of them.
> 
Sounds good.

> Got sucked into the "discussion" of the stable kernels on Friday and
> didn't do the update like I was wanting to do so :)
> 
In this context ... you are doing an amazing job with -stable.
I have no idea how you manage to do that, especially with all your other
responsibilities. If anything, it is unfair to talk about an allegedly
"broken" process if so much of it depends on a single person.
stable_kernel_rules talks about a review committee. Unless I am missing
something, that committee consists of one person. Maybe it would help
to add a couple more. Good candidates might be the people who are
complaining about a broken process ;).

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