From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Dennis Zhou <dennis@kernel.org>
Cc: Uros Bizjak <ubizjak@gmail.com>,
x86@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-bcachefs@vger.kernel.org,
linux-arch@vger.kernel.org, netdev@vger.kernel.org,
Nadav Amit <nadav.amit@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Brian Gerst <brgerst@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 5/6] percpu: Repurpose __percpu tag as a named address space qualifier
Date: Fri, 6 Dec 2024 11:07:53 -0800 (PST) [thread overview]
Message-ID: <b95641e3-39e1-01f0-54ff-000d860516cb@gentwo.org> (raw)
In-Reply-To: <Z1KpWenJGqhjtNL9@V92F7Y9K0C.lan>
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.
next prev parent reply other threads:[~2024-12-06 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 15:40 [PATCH v2 0/6] Enable strict percpu address space checks Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 1/6] x86/kgdb: Use IS_ERR_PCPU() macro Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 2/6] compiler.h: Introduce TYPEOF_UNQUAL() macro Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 3/6] percpu: Use TYPEOF_UNQUAL() in variable declarations Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 4/6] percpu: Use TYPEOF_UNQUAL() in *_cpu_ptr() accessors Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 5/6] percpu: Repurpose __percpu tag as a named address space qualifier Uros Bizjak
2024-12-06 7:35 ` Dennis Zhou
2024-12-06 19:07 ` Christoph Lameter (Ampere) [this message]
2024-12-06 20:13 ` Uros Bizjak
2024-12-05 15:40 ` [PATCH v2 6/6] percpu/x86: Enable strict percpu checks via named AS qualifiers Uros Bizjak
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=b95641e3-39e1-01f0-54ff-000d860516cb@gentwo.org \
--to=cl@gentwo.org \
--cc=arnd@arndb.de \
--cc=brgerst@gmail.com \
--cc=dennis@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=nadav.amit@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--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