From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-mm@kvack.org, Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH v2 1/2] mm/memblock: expose only miminal interface to add/walk physmem
Date: Fri, 3 Jul 2020 10:31:54 +0200 [thread overview]
Message-ID: <20200703083154.GD4582@osiris> (raw)
In-Reply-To: <20200702214852.f6ab03dc8d072abf35359d3b@linux-foundation.org>
On Thu, Jul 02, 2020 at 09:48:52PM -0700, Andrew Morton wrote:
> On Thu, 2 Jul 2020 09:23:10 +0200 David Hildenbrand <david@redhat.com> wrote:
>
> > >>> ---
> > >>> arch/s390/kernel/crash_dump.c | 6 ++--
> > >>> include/linux/memblock.h | 28 ++++++++++++++---
> > >>> mm/memblock.c | 57 ++++++++++++++++++-----------------
> > >>> 3 files changed, 55 insertions(+), 36 deletions(-)
> > >
> > > So I guess this should go via the s390 tree, since the second patch of
> > > this series can go only upstream if both this patch and a patch which
> > > is currently only on our features are merged before.
> > >
> > > Any objections?
> >
> > @Andrew, fine with you if this goes via the s390 tree?
>
> Sure, please go ahead.
Ok, applied both patches. Thanks!
next prev parent reply other threads:[~2020-07-03 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 14:18 [PATCH v2 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK David Hildenbrand
2020-07-01 14:18 ` [PATCH v2 1/2] mm/memblock: expose only miminal interface to add/walk physmem David Hildenbrand
2020-07-01 15:06 ` Mike Rapoport
2020-07-01 15:31 ` Heiko Carstens
2020-07-01 16:28 ` Mike Rapoport
2020-07-02 7:23 ` David Hildenbrand
2020-07-03 4:48 ` Andrew Morton
2020-07-03 8:31 ` Heiko Carstens [this message]
2020-07-01 15:34 ` David Hildenbrand
2020-07-01 15:36 ` Heiko Carstens
2020-07-01 14:18 ` [PATCH v2 2/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK David Hildenbrand
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=20200703083154.GD4582@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=rppt@linux.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 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.