From: Jakub Kicinski <kuba@kernel.org>
To: Bo Liu <liubo03@inspur.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ethtool: pse-pd: Fix double word in comments
Date: Mon, 20 Feb 2023 16:27:55 -0800 [thread overview]
Message-ID: <20230220162755.264c162c@kernel.org> (raw)
In-Reply-To: <20230217071609.2776-1-liubo03@inspur.com>
On Fri, 17 Feb 2023 02:16:09 -0500 Bo Liu wrote:
> Remove the repeated word "for" in comments.
>
> Signed-off-by: Bo Liu <liubo03@inspur.com>
Please resend with appropriate CC as instructed by Andrew.
next prev parent reply other threads:[~2023-02-21 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 7:16 [PATCH] ethtool: pse-pd: Fix double word in comments Bo Liu
2023-02-18 0:51 ` Andrew Lunn
2023-02-21 0:27 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 8:30 Bo Liu
2023-02-21 8:32 ` Oleksij Rempel
2023-02-21 16:31 ` Simon Horman
2023-02-21 17:01 ` Jakub Kicinski
2023-02-22 8:14 ` Simon Horman
2023-02-21 17:10 ` patchwork-bot+netdevbpf
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=20230220162755.264c162c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).