From: Simon Horman <horms@kernel.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, skhan@linuxfoundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] net: ipconfig: replace strncpy with strscpy
Date: Sat, 7 Jun 2025 17:42:00 +0100 [thread overview]
Message-ID: <20250607164200.GC197663@horms.kernel.org> (raw)
In-Reply-To: <20250607152830.26597-1-pranav.tyagi03@gmail.com>
On Sat, Jun 07, 2025 at 08:58:30PM +0530, Pranav Tyagi wrote:
> Replace the deprecated strncpy() with strscpy() as the destination
> buffer is NUL-terminated and does not require any
> trailing NUL-padding. Also increase the length to 252
> as NUL-termination is guaranteed.
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
Hi Pranav,
As a non-bug fix for Networking code this should be targeted
at net-next. And it's helpful to do so explicitly in the patch subject,
like this:
[PATCH v2 net-next] ...
Also, unfortunately the timing of this patch is not good
as net-next is currently closed for the merge window.
You can find more information about the above,
and other aspects of the workflow for the Networking subsystem
in https://docs.kernel.org/process/maintainer-netdev.html
## 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.
--
pw-bot: defer
next prev parent reply other threads:[~2025-06-07 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 15:28 [PATCH] net: ipconfig: replace strncpy with strscpy Pranav Tyagi
2025-06-07 16:42 ` Simon Horman [this message]
2025-06-11 14:12 ` Pranav Tyagi
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=20250607164200.GC197663@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.