[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCRgRxmO6rsR-0k3@gmail.com>
Date: Wed, 14 May 2025 11:20:07 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Shivank Garg <shivankg@....com>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
luto@...nel.org, peterz@...radead.org, rafael@...nel.org,
pavel@...nel.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
sohil.mehta@...el.com, rui.zhang@...el.com, yuntao.wang@...ux.dev,
kai.huang@...el.com, xiaoyao.li@...el.com, peterx@...hat.com,
sandipan.das@....com, ak@...ux.intel.com, rostedt@...dmis.org
Subject: Re: [PATCH RESEND 1/4] x86/mm: pgtable: Fix W=1 build kernel-doc
warnings
* Shivank Garg <shivankg@....com> wrote:
> >> @@ -665,6 +665,9 @@ void native_set_fixmap(unsigned /* enum fixed_addresses */ idx,
> >> #ifdef CONFIG_X86_5LEVEL
> >> /**
> >> * p4d_set_huge - setup kernel P4D mapping
> >> + * @p4d: Pointer to a p4d entry.
> >> + * @addr: Virtual Address associated with p4d.
> >> + * @prot: Protection bits to use.
> >
> > How about using the same capitalization you already see in this
> > description?
> Please review the revised patch with suggested changes.
I think you misunderstood: why are you using 'p4d', while a line before
it's 'P4D'? It's an acronym, and only used lowercase when it's a local
variable. 'p4d is a pointer to a p4d entry' is doubly confusing in that
regard ...
Same for PMD/PUD etc.
Thanks,
Ingo
Powered by blists - more mailing lists