From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Rusty Russell <rusty@rustcorp.com.au>,
Anthony Liguori <aliguori@us.ibm.com>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-s390@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 4/4] s390: remove s390_root_dev_*()
Date: Fri, 12 Dec 2008 10:54:05 +0100 [thread overview]
Message-ID: <1229075645.28887.10.camel@localhost> (raw)
In-Reply-To: <1229075116.28887.4.camel@localhost>
On Fri, 2008-12-12 at 10:45 +0100, Martin Schwidefsky wrote:
> On Fri, 2008-12-12 at 09:35 +0000, Mark McLoughlin wrote:
> > From: Mark McLoughlin <markmc@redhat.com>
> > Subject: [PATCH] s390: remove s390_root_dev_*()
> >
> > Replace s390_root_dev_register() with root_device_register() etc.
> >
> > [Includes fix from Cornelia Huck]
> >
> > Signed-off-by: Mark McLoughlin <markmc@redhat.com>
>
> I can carry the patch in my patch queue. Thanks.
Oops, this depends on another patch. If the other patch is missing it
doesn't compile.. So I better not add that patch to my queue. It should
be sent together with the patch it depends on.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-12-12 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1229012203.7968.79.camel@blaa>
[not found] ` <1229012216-4211-1-git-send-email-markmc@redhat.com>
[not found] ` <1229012216-4211-2-git-send-email-markmc@redhat.com>
[not found] ` <1229012216-4211-3-git-send-email-markmc@redhat.com>
[not found] ` <1229012216-4211-4-git-send-email-markmc@redhat.com>
2008-12-11 17:00 ` [PATCH 4/4] s390: remove s390_root_dev_*() Cornelia Huck
2008-12-12 9:29 ` Cornelia Huck
2008-12-12 9:35 ` Mark McLoughlin
2008-12-12 9:45 ` Martin Schwidefsky
2008-12-12 9:54 ` Martin Schwidefsky [this message]
2008-12-12 9:45 ` Cornelia Huck
2008-12-12 19:07 ` Greg KH
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=1229075645.28887.10.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.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