From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: robh+dt@kernel.org, frowand.list@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: base: fix repeated words in comments
Date: Sun, 18 Sep 2022 21:03:46 +0700 [thread overview]
Message-ID: <YyclQlws9d7vheDk@debian.me> (raw)
In-Reply-To: <20220918095957.24537-1-yuanjilin@cdjrlc.com>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
On Sun, Sep 18, 2022 at 05:59:57PM +0800, Jilin Yuan wrote:
> /**
> * of_match_node - Tell if a device_node has a matching of_match structure
> - * @matches: array of of device match structures to search in
> + * @matches: array of device match structures to search in
> * @node: the of device structure to match against
> *
> * Low level utility function used by device matching.
> @@ -1175,7 +1175,7 @@ EXPORT_SYMBOL(of_match_node);
> * you pass will not be searched, only the next one
> * will; typically, you pass what the previous call
> * returned. of_node_put() will be called on it
> - * @matches: array of of device match structures to search in
> + * @matches: array of device match structures to search in
> * @match: Updated to point at the matches entry which matched
That second "of" is the device, so the fix doesn't make sense.
Also, PLEASE stop sending these mindless redundant word-stripping patches
as byproduct of whatever automated tool you use.
As Edward Cree said to one of your colleague [1]:
> #ifdef RANT
> NGL, getting kinda sick of these bogus comment text 'fixes' from people
> who clearly don't have enough mastery of English to copyedit it.
> (Previous one from this author was actually wrong too but I didn't catch
> it at the time.)
> English is a tricksy language, why would someone with a limited
> understanding of it think that grammar fixes are the best use of their
> time and energy?
> I can't help suspecting that this is a box-ticking exercise, where a
> certain corporate culture has a standard requirement that engineers
> must get X number of Linux / opensource commits in order to get
> promoted, and this kind of mindless patch is the easiest way for them
> to achieve that.
> #endif
If you really want to do real cleanup, consider joining kernel-janitors list.
Learn from above, thanks.
[1]: https://lore.kernel.org/netdev/30f2488d-9af3-fe8d-6e6f-713a7d38800b@gmail.com/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-09-18 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 9:59 [PATCH] of: base: fix repeated words in comments Jilin Yuan
2022-09-18 14:03 ` Bagas Sanjaya [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=YyclQlws9d7vheDk@debian.me \
--to=bagasdotme@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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