linux-kernel - Re: [git pull] Input patches for 2.6.20

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:	Fri, 4 May 2007 23:03:38 -0700
From:	Greg KH <gregkh@...e.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	Cornelia Huck <cornelia.huck@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] Input patches for 2.6.20

On Fri, May 04, 2007 at 06:19:49PM -0700, Linus Torvalds wrote:
> 
> 
> On Thu, 3 May 2007, Dmitry Torokhov wrote:
> > 
> > If you have not pulled yet please pull from:
> >
> > ?? ?? ?? ?? master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
> > 
> > because master branch will have extra stuff in the next minute or so.
> 
> Hmm. That thing had a conflict with the driver core changes I just pulled 
> from Greg due to Greg removing "struct subsystem".
> 
> The conflict looked really trivial, and I fixed up the obvious places, 
> probably correctly. Please verify.
> 
> Martin, in the process I noticed that the new file
> 
> 	arch/s390/kernel/ipl.c
> 
> seems to be broken by the same thing after the driver core merge. The fix 
> _looks_ equally trivial (change *subsys.kset.kobj into just *subsys.kobj), 
> but I didn't do that trivial thing, because I cannot even test-compile the 
> end result. So can you give it a quick look, please?

Martin, Cornelia already sent me (and lkml) a patch to fix this all up
if you want to just use that instead.

> Greg - maybe more of a heads-up to people next time you do something like 
> this? Did this removal hit -mm? Anyway, it looks like something trivial to 
> fix up after, but ..

Yes, this was in -mm for quite a while, and yes, I knew about the
conflict with the input tree, that's why I waited to send this to you
separate from the first merge set and in the second batch, thinking that
either had already sent his stuff, or was going to do so afterwards, and
would be trivial to fix up.

Sorry about that, sometimes core changes like this take a bit of
coordination across subsystems.

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/