From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oomichi@mxs.nes.nec.co.jp, linux-s390@vger.kernel.org,
mahesh@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
linux-kernel@vger.kernel.org, hbabu@us.ibm.com,
horms@verge.net.au, ebiederm@xmission.com,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
kexec@lists.infradead.org, vgoyal@redhat.com
Subject: Re: [patch 0/2] kdump: Common code changes for s390 kdump support
Date: Mon, 22 Aug 2011 08:34:59 +0200 [thread overview]
Message-ID: <20110822083459.2cc52fc8@mschwide> (raw)
In-Reply-To: <20110819150353.bf58c7e0.akpm@linux-foundation.org>
On Fri, 19 Aug 2011 15:03:53 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 19 Aug 2011 16:18:57 +0200
> Michael Holzheu <holzheu@linux.vnet.ibm.com> wrote:
>
> > I had a long discussion with Vivek Goyal on the s390 kdump support (thanks
> > Vivek for all the time!). As a result of this, here are two common code
> > patches that are required for the s390 port. Could you please integrate them
> > upstream in the next merge window? The s390 specific part will be integrated
> > by our s390 maintainer Martin Schwidefsky.
>
> The patches look OK to me. I suggest that they be carried in Martin's
> tree, alongside the s390 kdump support. That will somewhat simplify
> things during the merge window, and will greatly simplify getting the
> entire feature into linux-next.
>
> You can put my acked-by's on them if you like.
>
> > I will be on vacation for the next two weeks. Therefore if you have comments
> > or questions, please contact also Martin Schwidefsky and Heiko Carstens.
>
> I'll put the patches into my tree (and hence linux-next) now, because I
> need the typing practice ;) I'll drop them again if/when they turn up
> in linux-next's s390 tree.
Ok, sounds reasonable to me. I'll take them via the s390 tree and add
you acked-by. Thanks Andrew.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
vgoyal@redhat.com, ebiederm@xmission.com,
mahesh@linux.vnet.ibm.com, hbabu@us.ibm.com,
oomichi@mxs.nes.nec.co.jp, horms@verge.net.au,
heiko.carstens@de.ibm.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [patch 0/2] kdump: Common code changes for s390 kdump support
Date: Mon, 22 Aug 2011 08:34:59 +0200 [thread overview]
Message-ID: <20110822083459.2cc52fc8@mschwide> (raw)
In-Reply-To: <20110819150353.bf58c7e0.akpm@linux-foundation.org>
On Fri, 19 Aug 2011 15:03:53 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 19 Aug 2011 16:18:57 +0200
> Michael Holzheu <holzheu@linux.vnet.ibm.com> wrote:
>
> > I had a long discussion with Vivek Goyal on the s390 kdump support (thanks
> > Vivek for all the time!). As a result of this, here are two common code
> > patches that are required for the s390 port. Could you please integrate them
> > upstream in the next merge window? The s390 specific part will be integrated
> > by our s390 maintainer Martin Schwidefsky.
>
> The patches look OK to me. I suggest that they be carried in Martin's
> tree, alongside the s390 kdump support. That will somewhat simplify
> things during the merge window, and will greatly simplify getting the
> entire feature into linux-next.
>
> You can put my acked-by's on them if you like.
>
> > I will be on vacation for the next two weeks. Therefore if you have comments
> > or questions, please contact also Martin Schwidefsky and Heiko Carstens.
>
> I'll put the patches into my tree (and hence linux-next) now, because I
> need the typing practice ;) I'll drop them again if/when they turn up
> in linux-next's s390 tree.
Ok, sounds reasonable to me. I'll take them via the s390 tree and add
you acked-by. Thanks Andrew.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2011-08-22 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 14:18 [patch 0/2] kdump: Common code changes for s390 kdump support Michael Holzheu
2011-08-19 14:18 ` Michael Holzheu
2011-08-19 14:18 ` [patch 1/2] kdump: Add KEXEC_CRASH_CONTROL_MEMORY_LIMIT Michael Holzheu
2011-08-19 14:18 ` Michael Holzheu
2011-08-19 14:24 ` Vivek Goyal
2011-08-19 14:24 ` Vivek Goyal
2011-08-19 14:18 ` [patch 2/2] kdump: Add size to elfcorehdr kernel parameter Michael Holzheu
2011-08-19 14:18 ` Michael Holzheu
2011-08-19 14:25 ` Vivek Goyal
2011-08-19 14:25 ` Vivek Goyal
2011-08-19 22:03 ` [patch 0/2] kdump: Common code changes for s390 kdump support Andrew Morton
2011-08-19 22:03 ` Andrew Morton
2011-08-22 6:34 ` Martin Schwidefsky [this message]
2011-08-22 6:34 ` 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=20110822083459.2cc52fc8@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.