From: Simon Horman <simon.horman@corigine.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Bo Liu <liubo03@inspur.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux@rempel-privat.de, bagasdotme@gmail.com, andrew@lunn.ch,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethtool: pse-pd: Fix double word in comments
Date: Wed, 22 Feb 2023 09:14:45 +0100 [thread overview]
Message-ID: <Y/XO9cxFOkChm3Je@corigine.com> (raw)
In-Reply-To: <20230221090159.4fa9a548@kernel.org>
On Tue, Feb 21, 2023 at 09:01:59AM -0800, Jakub Kicinski wrote:
> On Tue, 21 Feb 2023 17:31:00 +0100 Simon Horman wrote:
> > On Tue, Feb 21, 2023 at 03:30:36AM -0500, Bo Liu wrote:
> > > Remove the repeated word "for" in comments.
> > >
> > > Signed-off-by: Bo Liu <liubo03@inspur.com>
> >
> > net-next is closed.
> >
> > You'll need to repost this patch after v6.3-rc1 has been tagged.
> >
> > Also, when reposting please indicate that it is targeted
> > at net-next by including [PATCH net-next] in the subject.
> >
> > Ref: https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
>
> I was planning on applying it, actually, it's just a comment change
> and PR is not yet out.
Sorry, my mistake.
next prev parent reply other threads:[~2023-02-22 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 8:30 [PATCH] ethtool: pse-pd: Fix double word in comments 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 [this message]
2023-02-21 17:10 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 7:16 Bo Liu
2023-02-18 0:51 ` Andrew Lunn
2023-02-21 0:27 ` Jakub Kicinski
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/XO9cxFOkChm3Je@corigine.com \
--to=simon.horman@corigine.com \
--cc=andrew@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--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).