From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>, <x86@kernel.org>
Cc: <tglx@linutronix.de>, <bp@alien8.de>, <hpa@zytor.com>,
<mingo@redhat.com>
Subject: Re: [PATCH] x86/fixmap: update stale comments
Date: Thu, 15 Aug 2019 10:44:33 +0800 [thread overview]
Message-ID: <69f31bf8-e957-951c-9c18-9a804ee770b7@cn.fujitsu.com> (raw)
In-Reply-To: <20190809114612.2569-1-caoj.fnst@cn.fujitsu.com>
Hi,
Wish to know whether the patch make sense.
On 8/9/19 7:46 PM, Cao jin wrote:
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> arch/x86/include/asm/fixmap.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/fixmap.h b/arch/x86/include/asm/fixmap.h
> index 9da8cccdf3fb..0c47aa82e2e2 100644
> --- a/arch/x86/include/asm/fixmap.h
> +++ b/arch/x86/include/asm/fixmap.h
> @@ -42,8 +42,7 @@
> * Because of this, FIXADDR_TOP x86 integration was left as later work.
> */
> #ifdef CONFIG_X86_32
> -/* used by vmalloc.c, vsyscall.lds.S.
> - *
> +/*
Not seeing variable __FIXADDR_TOP & macro FIXADDR_TOP under
CONFIG_X86_32 referred in vmalloc.c, and there is no vsyscall.lds.S now.
> * Leave one empty page between vmalloc'ed areas and
> * the start of the fixmap.
> */
> @@ -120,7 +119,7 @@ enum fixed_addresses {
> * before ioremap() is functional.
> *
> * If necessary we round it up to the next 512 pages boundary so
> - * that we can have a single pgd entry and a single pte table:
> + * that we can have a single pmd entry and a single pte table:
The comments seems missed to be updated in an ancient commit 551889a6e2a24
> */
> #define NR_FIX_BTMAPS 64
> #define FIX_BTMAPS_SLOTS 8
>
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2019-08-15 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 11:46 Cao jin
2019-08-15 2:44 ` Cao jin [this message]
2019-08-23 2:12 ` [tip: x86/mm] x86/fixmap: Cleanup outdated comments tip-bot2 for Cao jin
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=69f31bf8-e957-951c-9c18-9a804ee770b7@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®