From: Helge Deller <deller@gmx.de>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: Kconfig: remove ARCH_DISCARD_MEMBLOCK
Date: Tue, 21 May 2019 19:16:56 +0200 [thread overview]
Message-ID: <f88c865d-b571-8539-8b5d-4881f076e084@gmx.de> (raw)
In-Reply-To: <20190521155440.GD24470@rapoport-lnx>
On 21.05.19 17:54, Mike Rapoport wrote:
> Gentle ping ...
No need to hurry.
It's already included in my git for-next tree:
https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next
Helge
>
> On Wed, May 15, 2019 at 08:41:22AM +0300, Mike Rapoport wrote:
>> Since commit 350e88bad496 ("mm: memblock: make keeping memblock memory
>> opt-in rather than opt-out") the default behaviour is to discard memblock
>> data after init and the ARCH_DISCARD_MEMBLOCK is obsolete.
>>
>> Remove it.
>>
>> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
>> ---
>> arch/parisc/Kconfig | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/parisc/Kconfig b/arch/parisc/Kconfig
>> index 09407ed..13b95125 100644
>> --- a/arch/parisc/Kconfig
>> +++ b/arch/parisc/Kconfig
>> @@ -36,7 +36,6 @@ config PARISC
>> select GENERIC_STRNCPY_FROM_USER
>> select SYSCTL_ARCH_UNALIGN_ALLOW
>> select SYSCTL_EXCEPTION_TRACE
>> - select ARCH_DISCARD_MEMBLOCK
>> select HAVE_MOD_ARCH_SPECIFIC
>> select VIRT_TO_BUS
>> select MODULES_USE_ELF_RELA
>> --
>> 2.7.4
>>
>
prev parent reply other threads:[~2019-05-21 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 5:41 [PATCH] parisc: Kconfig: remove ARCH_DISCARD_MEMBLOCK Mike Rapoport
2019-05-21 15:54 ` Mike Rapoport
2019-05-21 17:16 ` Helge Deller [this message]
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=f88c865d-b571-8539-8b5d-4881f076e084@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).