All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm@kvack.org, Will Deacon <will@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Generalize ARCH_HAS_FILTER_PGPROT
Date: Mon, 10 Jan 2022 17:13:07 +0530	[thread overview]
Message-ID: <de9ce5d0-04f0-74c5-a65c-814acedb5d46@arm.com> (raw)
In-Reply-To: <YdwP40C8Zu8s2Az0@arm.com>



On 1/10/22 4:22 PM, Catalin Marinas wrote:
> On Mon, Jan 10, 2022 at 12:11:36PM +0530, Anshuman Khandual wrote:
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 5c2ccb85f2ef..d9594e05fddb 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -328,9 +328,6 @@ config GENERIC_CALIBRATE_DELAY
>>  config ARCH_HAS_CPU_RELAX
>>  	def_bool y
>>  
>> -config ARCH_HAS_FILTER_PGPROT
>> -	def_bool y
> 
> Aren't you missing a select for x86?
> 

It already gets unconditionally selected in arch/x86/Kconfig.

WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm@kvack.org, Will Deacon <will@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arm-kernel@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Generalize ARCH_HAS_FILTER_PGPROT
Date: Mon, 10 Jan 2022 17:13:07 +0530	[thread overview]
Message-ID: <de9ce5d0-04f0-74c5-a65c-814acedb5d46@arm.com> (raw)
In-Reply-To: <YdwP40C8Zu8s2Az0@arm.com>



On 1/10/22 4:22 PM, Catalin Marinas wrote:
> On Mon, Jan 10, 2022 at 12:11:36PM +0530, Anshuman Khandual wrote:
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 5c2ccb85f2ef..d9594e05fddb 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -328,9 +328,6 @@ config GENERIC_CALIBRATE_DELAY
>>  config ARCH_HAS_CPU_RELAX
>>  	def_bool y
>>  
>> -config ARCH_HAS_FILTER_PGPROT
>> -	def_bool y
> 
> Aren't you missing a select for x86?
> 

It already gets unconditionally selected in arch/x86/Kconfig.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-10 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  6:41 [PATCH] mm: Generalize ARCH_HAS_FILTER_PGPROT Anshuman Khandual
2022-01-10 10:52 ` Catalin Marinas
2022-01-10 10:52   ` Catalin Marinas
2022-01-10 11:43   ` Anshuman Khandual [this message]
2022-01-10 11:43     ` Anshuman Khandual
2022-01-11 10:19 ` Catalin Marinas
2022-01-11 10:19   ` Catalin Marinas
2022-01-24  6:13 Anshuman Khandual

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=de9ce5d0-04f0-74c5-a65c-814acedb5d46@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.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 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.