From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Devicetree <devicetree@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Jiang Jian <jiangjian@cdjrlc.com>,
wangjianli <wangjianli@cdjrlc.com>,
Jilin Yuan <yuanjilin@cdjrlc.com>
Subject: Re: [PATCH] of: Clarify OF device context in of_match_device() comment
Date: Wed, 30 Jul 2025 12:23:40 -0700 [thread overview]
Message-ID: <f5537798-1227-40b8-8ab9-6dd104e245e7@infradead.org> (raw)
In-Reply-To: <20250730013113.11264-1-bagasdotme@gmail.com>
On 7/29/25 6:31 PM, Bagas Sanjaya wrote:
> Open Firmware abbreviation (OF) in of_match_device() comment is written
> in lowercase instead, which is mistaken for prepositional word "of"
> ([1], [2], [3], [4]) duplicate.
>
> Clarify the context.
>
> Link: https://lore.kernel.org/all/CAL_JsqLypcBCOVZ8yYWK0J_xc2Vcr+ANrX_3v4vN55Srp4RknQ@mail.gmail.com/ [1]
> Link: https://lore.kernel.org/all/20220926185852.GA2581083-robh@kernel.org/ [2]
> Link: https://lore.kernel.org/all/CAL_JsqL4GvgFYzGUfhW5pvm4wYGrFaj6gHOYZjnOMuk2zCz67w@mail.gmail.com/ [3]
> Link: https://lore.kernel.org/all/20220627173825.GA2637590-robh@kernel.org/ [4]
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Wow, that's confusing (the "of" parts).
Hopefully Rob won't mind losing the entertainment factor here.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/of/device.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/of/device.c b/drivers/of/device.c
> index c80426510ec2c0..f7e75e5276677e 100644
> --- a/drivers/of/device.c
> +++ b/drivers/of/device.c
> @@ -17,8 +17,8 @@
>
> /**
> * of_match_device - Tell if a struct device matches an of_device_id list
> - * @matches: array of of device match structures to search in
> - * @dev: the of device structure to match against
> + * @matches: array of of_device_id match structures to search in
> + * @dev: the OF device structure to match against
> *
> * Used by a driver to check whether an platform_device present in the
> * system is in its list of supported devices.
>
> base-commit: 0121898ec05fa4c1f566fc05c7e8b3caf0998f97
--
~Randy
next prev parent reply other threads:[~2025-07-30 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 1:31 [PATCH] of: Clarify OF device context in of_match_device() comment Bagas Sanjaya
2025-07-30 19:23 ` Randy Dunlap [this message]
2025-07-30 22:49 ` Rob Herring (Arm)
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=f5537798-1227-40b8-8ab9-6dd104e245e7@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jiangjian@cdjrlc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=wangjianli@cdjrlc.com \
--cc=yuanjilin@cdjrlc.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;
as well as URLs for NNTP newsgroup(s).