linux-kernel - Re: [PATCH 19/62] Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default

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:	Wed, 3 Mar 2010 14:04:50 -0800
From:	Greg KH <gregkh@...e.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH 19/62] Driver-Core: devtmpfs - remove EXPERIMENTAL and
 enable it by default

On Wed, Mar 03, 2010 at 01:48:08PM -0800, Linus Torvalds wrote:
> 
> Anyway, I don't know whether you picked a good spot to do your series or 
> not, but it _looked_ like a pretty random spot. It might be perfectly 
> good. But just in general, since you always generate your trees from a 
> quilt series anyway, I suspect we migth be better off (at least for the 
> initial merge window series) to base them on the closest thing we have to 
> a "known good" base, namely the previous release. Rather than some "maybe 
> fine" point in the middle of the merge window.

I originally did the create from the 2.6.33 release, and then did a
merge to test that it would be easy for you, but there were a number of
conflicts due to other trees touching some driver core stuff (that I
knew was going to happen.)  So I did take a merge point after that had
happened, and did test it out here on my machines.

But hey, if you want to have to handle merge conflicts, I'll gladly base
them on known-common points in the future :)

In the future I'll try to pick better merge points.

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/