From: Jan Kiszka <jan.kiszka@web.de>
To: Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: x86 <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86: pat: Do not compile stubbed functions when X86_PAT is off
Date: Sun, 11 Apr 2021 10:22:19 +0200 [thread overview]
Message-ID: <802cefc7-b475-c6d6-ece7-8232d7f3891d@web.de> (raw)
In-Reply-To: <a9351615-7a0d-9d47-af65-d9e2fffe8192@siemens.com>
On 26.10.20 18:39, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Those are already provided by linux/io.h as stubs.
>
> The conflict remains invisible until someone would pull linux/io.h into
> memtype.c.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> Change in v2:
> - correct commit message
>
> arch/x86/mm/pat/memtype.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/x86/mm/pat/memtype.c b/arch/x86/mm/pat/memtype.c
> index 8f665c352bf0..41a4ac585af3 100644
> --- a/arch/x86/mm/pat/memtype.c
> +++ b/arch/x86/mm/pat/memtype.c
> @@ -800,6 +800,7 @@ void memtype_free_io(resource_size_t start, resource_size_t end)
> memtype_free(start, end);
> }
>
> +#ifdef CONFIG_X86_PAT
> int arch_io_reserve_memtype_wc(resource_size_t start, resource_size_t size)
> {
> enum page_cache_mode type = _PAGE_CACHE_MODE_WC;
> @@ -813,6 +814,7 @@ void arch_io_free_memtype_wc(resource_size_t start, resource_size_t size)
> memtype_free_io(start, start + size);
> }
> EXPORT_SYMBOL(arch_io_free_memtype_wc);
> +#endif
>
> pgprot_t phys_mem_access_prot(struct file *file, unsigned long pfn,
> unsigned long size, pgprot_t vma_prot)
>
What happened to this?
Jan
next prev parent reply other threads:[~2021-04-11 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 14:55 [PATCH] " Jan Kiszka
2020-02-07 14:50 ` Thomas Gleixner
2020-02-07 15:02 ` Jan Kiszka
2020-10-26 17:39 ` [PATCH v2] " Jan Kiszka
2021-04-11 8:22 ` Jan Kiszka [this message]
2021-04-11 9:10 ` Borislav Petkov
2021-04-11 9:12 ` Jan Kiszka
2021-04-11 9:25 ` Borislav Petkov
2021-04-14 7:36 ` [tip: x86/cleanups] x86/pat: " tip-bot2 for Jan Kiszka
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=802cefc7-b475-c6d6-ece7-8232d7f3891d@web.de \
--to=jan.kiszka@web.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®