From: Rob Herring <robh+dt@kernel.org>
To: wangjianli <wangjianli@cdjrlc.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/of: fix repeated words in comments
Date: Sun, 21 Aug 2022 13:48:11 -0500 [thread overview]
Message-ID: <CAL_JsqL4GvgFYzGUfhW5pvm4wYGrFaj6gHOYZjnOMuk2zCz67w@mail.gmail.com> (raw)
In-Reply-To: <20220821151123.54778-1-wangjianli@cdjrlc.com>
On Sun, Aug 21, 2022 at 10:11 AM wangjianli <wangjianli@cdjrlc.com> wrote:
>
> Delete the redundant word 'of'.
>
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> drivers/of/device.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Same comments as last time I got this fix:
https://lore.kernel.org/all/20220627173825.GA2637590-robh@kernel.org/
Rob
prev parent reply other threads:[~2022-08-21 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 15:11 [PATCH] drivers/of: fix repeated words in comments wangjianli
2022-08-21 18:48 ` Rob Herring [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=CAL_JsqL4GvgFYzGUfhW5pvm4wYGrFaj6gHOYZjnOMuk2zCz67w@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wangjianli@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).