From: Paolo Abeni <pabeni@redhat.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, darren.kenny@oracle.com
Subject: Re: [PATCH RESEND] selftests: nettest: Fix typo in log and error messages for clarity
Date: Mon, 26 May 2025 18:01:35 +0200 [thread overview]
Message-ID: <18051f57-37c7-4994-8859-d0c41ef6fb7d@redhat.com> (raw)
In-Reply-To: <20250526151636.1485230-1-alok.a.tiwari@oracle.com>
On 5/26/25 5:16 PM, Alok Tiwari wrote:
> This patch corrects several logging and error message typos in nettest.c:
> - Corrects function name in log messages "setsockopt" -> "getsockopt".
> - Closes missing parentheses in "setsockopt(IPV6_FREEBIND)".
> - Replaces misleading error text ("Invalid port") with the correct
> description ("Invalid prefix length").
> - remove Redundant wording like "status from status" and clarifies
> context in IPC error messages.
>
> These changes improve readability and aid in debugging test output.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
> Resending: Previous email used incorrect address for David S. Miller
You should have waited the 24h grace period before resending:
https://elixir.bootlin.com/linux/v6.15/source/Documentation/process/maintainer-netdev.rst#L15
---
## Form letter - net-next-closed
The merge window for v6.16 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations. We are
currently accepting bug fixes only.
Please repost when net-next reopens after June 8th.
RFC patches sent for review only are obviously welcome at any time.
prev parent reply other threads:[~2025-05-26 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:16 Alok Tiwari
2025-05-26 16:01 ` Paolo Abeni [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=18051f57-37c7-4994-8859-d0c41ef6fb7d@redhat.com \
--to=pabeni@redhat.com \
--cc=alok.a.tiwari@oracle.com \
--cc=darren.kenny@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®