From: Joe Perches <joe@perches.com>
To: Mauro Codella <mauro.codella@pm.me>
Cc: corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: checkpatch: Fix DEVICE_ATTR_WO macro name
Date: Sat, 07 Nov 2026 18:18:16 -0800 [thread overview]
Message-ID: <5f6243cd0c0d26e89d9ef17abb68fcec240fa3dd.camel@perches.com> (raw)
In-Reply-To: <20261107230208.326769-1-mauro.codella@pm.me>
On Sat, 2026-11-07 at 23:02 +0000, Mauro Codella wrote:
> The DEVICE_ATTR_WO section refers to DEVICE_AATR_WO, which does not
> exist. Correct the spelling to match the macro in include/linux/device.h.
Thanks.
Acked-by: Joe Perches <joe@perches.com>
>
> Signed-off-by: Mauro Codella <mauro.codella@pm.me>
> ---
> AI assistance: Codex identified the typo and drafted the fix and commit
> message. I reviewed the change and ran checkpatch.
>
> Documentation/dev-tools/checkpatch.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/checkpatch.rst b/Documentation/dev-tools/checkpatch.rst
> index 6139a08c3..f8ab22c18 100644
> --- a/Documentation/dev-tools/checkpatch.rst
> +++ b/Documentation/dev-tools/checkpatch.rst
> @@ -389,7 +389,7 @@ API usage
> See: https://www.kernel.org/doc/html/latest/driver-api/driver-model/device.html#attributes
>
> **DEVICE_ATTR_WO**
> - The DEVICE_AATR_WO(name) helper macro can be used instead of
> + The DEVICE_ATTR_WO(name) helper macro can be used instead of
> DEVICE_ATTR(name, 0200, NULL, name_store);
>
> Note that the macro automatically appends _store to the
prev parent reply other threads:[~2026-11-08 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 23:02 Mauro Codella
2026-11-08 2:18 ` 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=5f6243cd0c0d26e89d9ef17abb68fcec240fa3dd.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauro.codella@pm.me \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.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
all inboxes | Powered by JetHome®