mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Liu Dalin <liudalin@kylinsec.com.cn>,
	Andy Whitcroft <apw@canonical.com>,
	 Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Ignore attribute macros ending with nGnRnE or nGnRE
Date: Sat, 07 Mar 2026 11:53:03 -0800	[thread overview]
Message-ID: <0168b7ac87d9bcd0a65f6ffad50816201719d4e3.camel@perches.com> (raw)
In-Reply-To: <1108F81575ADF445+20260307072754.111843-1-liudalin@kylinsec.com.cn>

On Sat, 2026-03-07 at 15:27 +0800, Liu Dalin wrote:
> On arm and arm64 platforms, there are several attribute macros that
> end with nGnRnE or nGnRE, such as PROT_DEVICE_nGnRnE, PROT_DEVICE_nGnRE,
> MT_DEVICE_nGnRnE, and MT_DEVICE_nGnRE.

+			    $var !~ /^[A-Z0-9_]+_(nGnRnE|nGnRE)$/) {

Maybe better if you add nGRE too and no capture group using (?:...)$

FYI: These appear unused to date:

$ git grep FFA_DEV
include/linux/arm_ffa.h:#define FFA_DEV_nGnRnE          (0 << 2)
include/linux/arm_ffa.h:#define FFA_DEV_nGnRE           (1 << 2)
include/linux/arm_ffa.h:#define FFA_DEV_nGRE            (2 << 2)
include/linux/arm_ffa.h:#define FFA_DEV_GRE             (3 << 2)

  reply	other threads:[~2026-03-07 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  7:27 Liu Dalin
2026-03-07 19:53 ` Joe Perches [this message]
2026-03-09  2:12   ` Liu Dalin
2026-03-09  2:47     ` Joe Perches
2026-03-09  3:02       ` Liu Dalin
2026-03-09  2:45 ` [PATCH 0/1] checkpatch: ignore memory attribute macros ending with nGnRnE, nGnRE, or nGRE Liu Dalin
     [not found] ` <20260309024545.122002-1-liudalin@kylinsec.com.cn>
2026-03-09  2:45   ` [PATCH 1/1] " Liu Dalin

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=0168b7ac87d9bcd0a65f6ffad50816201719d4e3.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liudalin@kylinsec.com.cn \
    --cc=lukas.bulwahn@gmail.com \
    /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®