From: Simon Horman <horms@kernel.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel-mentees@lists.linux.dev,
skhan@linuxfoundation.org
Subject: Re: [PATCH net-next] selftests: net: fix grammar in reuseaddr_ports_exhausted.c log message
Date: Sat, 15 Feb 2025 13:45:48 +0000 [thread overview]
Message-ID: <20250215134548.GN1615191@kernel.org> (raw)
In-Reply-To: <20250213152612.4434-1-pranav.tyagi03@gmail.com>
On Thu, Feb 13, 2025 at 08:56:11PM +0530, Pranav Tyagi wrote:
> This patch fixes a grammatical error in a test log message in
> reuseaddr_ports_exhausted.c for better clarity as a part of lfx
> application tasks
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
Thanks Pranav,
This change looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
A note on process to keep in mind for next time:
This patch seems to have been posted to netdev twice, about 20 hours apart.
Please don't do that as it can be quite confusing to reviewers.
If you need to update a patch, please version it (e.g. [PATCH v2 net-next).
If you need to repost a patch, say because there has been no response for a
long time, please label it accordingly (e.g. [PATCH REPOST net-next]) and
include some explanation of why it is being reposted, e.g. below the
scissors ("---").
And regardless, when posting a patch to netdev, please don't post it more
than once every 24h.
next prev parent reply other threads:[~2025-02-15 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 15:26 [PATCH net-next] selftests: net: fix grammar in reuseaddr_ports_exhausted.c log message Pranav Tyagi
2025-02-15 13:45 ` Simon Horman [this message]
2025-02-15 18:23 ` Pranav Tyagi
2025-02-16 9:32 ` Simon Horman
2025-02-18 0:40 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2025-02-12 18:54 Pranav Tyagi
2025-02-15 13:41 ` Simon Horman
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=20250215134548.GN1615191@kernel.org \
--to=horms@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pranav.tyagi03@gmail.com \
--cc=skhan@linuxfoundation.org \
/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).