From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: 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>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 1/2] mm/memblock: expose only miminal interface to add/walk physmem
Date: Wed, 1 Jul 2020 17:36:31 +0200 [thread overview]
Message-ID: <20200701153631.GD5008@osiris> (raw)
In-Reply-To: <62588A3E-81FA-4C79-B215-D1D33887597C@redhat.com>
> >> While fixing up the documentation, sneak in some related cleanups. We can
> >> stop setting CONFIG_HAVE_MEMBLOCK_PHYS_MAP for s390x next.
> > As you noted in the previous version it should have been
> > CONFIG_ARCH_KEEP_MEMBLOCK ;-)
> Grml :) maybe maintainers can fix that up when applying in case
> there are no other comments.
Sure, just need to know how to handle this. :)
next prev parent reply other threads:[~2020-07-01 15:36 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
2020-07-01 15:34 ` David Hildenbrand
2020-07-01 15:36 ` Heiko Carstens [this message]
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=20200701153631.GD5008@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.