From: Joe Perches <joe@perches.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] checkpatch: don't warn about complex macros in i.MX pin header
Date: Tue, 16 Dec 2025 17:11:26 +0700 [thread overview]
Message-ID: <fce65a7761fb0e880beb469e2521598f@perches.com> (raw)
In-Reply-To: <20251216-checkpatch-v1-1-8d7a40a10426@nxp.com>
On 2025-12-16 15:32, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> The pin function ID in i.MX pin headers is a tuple of <mux_reg conf_reg
> input_reg mux_mode input_val>, as below:
> "#define IMX95_PAD_DAP_TDI__JTAG_MUX_TDI 0x0000 0x0204 0x0610 0x00
> 0x00"
> The pin headers are used by device trees, not drivers.
Nak. Just ignore the message instead.
There would be _far_ too many exceptions to add individually to
checkpatch.
prev parent reply other threads:[~2025-12-16 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 8:32 Peng Fan (OSS)
2025-12-16 10:11 ` Joe Perches [this message]
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=fce65a7761fb0e880beb469e2521598f@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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®