[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b95641e3-39e1-01f0-54ff-000d860516cb@gentwo.org>
Date: Fri, 6 Dec 2024 11:07:53 -0800 (PST)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Dennis Zhou <dennis@...nel.org>
cc: Uros Bizjak <ubizjak@...il.com>, x86@...nel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-bcachefs@...r.kernel.org,
linux-arch@...r.kernel.org, netdev@...r.kernel.org,
Nadav Amit <nadav.amit@...il.com>, Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>, Tejun Heo <tj@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Brian Gerst <brgerst@...il.com>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2 5/6] percpu: Repurpose __percpu tag as a named address
space qualifier
On Thu, 5 Dec 2024, Dennis Zhou wrote:
> I read through the series and I think my only nit would be here. Can we
> name this __percpu_qual? My thoughts are that it keeps it consistent
> with the old address space identifier and largely most of the core
> percpu stuff is defined with percpu as the naming scheme.
Yes lets keep it consistent.
Powered by blists - more mailing lists