public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] Input patches for 2.6.20
Date: Fri, 4 May 2007 23:03:38 -0700	[thread overview]
Message-ID: <20070505060338.GA27713@suse.de> (raw)
In-Reply-To: <alpine.LFD.0.98.0705041806210.3808@woody.linux-foundation.org>

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

  reply	other threads:[~2007-05-05  6:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18  7:04 [git pull] Input patches for 2.6.20 Dmitry Torokhov
2007-05-03  5:07 ` Dmitry Torokhov
2007-05-05  1:19   ` Linus Torvalds
2007-05-05  6:03     ` Greg KH [this message]
2007-05-05  7:08       ` Andrew Morton
2007-05-05  8:51       ` Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070505060338.GA27713@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dtor@insightbb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox