From: Andrew Lunn <andrew@lunn.ch>
To: Bo Liu <liubo03@inspur.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethtool: pse-pd: Fix double word in comments
Date: Sat, 18 Feb 2023 01:51:09 +0100 [thread overview]
Message-ID: <Y/Ag/b8HAtqWlyfg@lunn.ch> (raw)
In-Reply-To: <20230217071609.2776-1-liubo03@inspur.com>
On Fri, Feb 17, 2023 at 02:16:09AM -0500, Bo Liu wrote:
> Remove the repeated word "for" in comments.
Hi Bo
How did you determine the list of people to email?
./scripts/get_maintainer.pl net/ethtool/pse-pd.c
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING [GENERAL],commit_signer:2/3=67%)
Eric Dumazet <edumazet@google.com> (maintainer:NETWORKING [GENERAL])
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING [GENERAL],commit_signer:3/3=100%,authored:2/3=67%,added_lines:30/215=14%,removed_lines:51/51=100%)
Paolo Abeni <pabeni@redhat.com> (maintainer:NETWORKING [GENERAL])
Oleksij Rempel <linux@rempel-privat.de> (commit_signer:2/3=67%,authored:1/3=33%,added_lines:185/215=86%)
Andrew Lunn <andrew@lunn.ch> (commit_signer:1/3=33%)
kernel test robot <lkp@intel.com> (commit_signer:1/3=33%)
netdev@vger.kernel.org (open list:NETWORKING [GENERAL])
linux-kernel@vger.kernel.org (open list)
Oleksij Rempel actually added this file, so you really should Cc: him,
even for trivial patches like this.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2023-02-18 0:51 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 [this message]
2023-02-21 0:27 ` Jakub Kicinski
-- 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=Y/Ag/b8HAtqWlyfg@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.