From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dmitry Torokhov <dtor@insightbb.com>, Greg KH <gregkh@suse.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: 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 18:19:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705041806210.3808@woody.linux-foundation.org> (raw)
In-Reply-To: <200705030107.44990.dtor@insightbb.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; CHARSET=us-ascii, Size: 1029 bytes --]
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?
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 ..
Linus
next prev parent reply other threads:[~2007-05-05 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 7:04 Dmitry Torokhov
2007-05-03 5:07 ` Dmitry Torokhov
2007-05-05 1:19 ` Linus Torvalds [this message]
2007-05-05 6:03 ` Greg KH
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=alpine.LFD.0.98.0705041806210.3808@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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
all inboxes | Powered by JetHome®