From: Jakub Kicinski <kuba@kernel.org>
To: <yang.yang29@zte.com.cn>
Cc: <salil.mehta@huawei.com>, <yisen.zhuang@huawei.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<brianvv@google.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <xu.panda@zte.com.cn>
Subject: Re: [PATCH linux-next] ethtool: use strscpy() to instead of strncpy()
Date: Thu, 8 Dec 2022 18:23:56 -0800 [thread overview]
Message-ID: <20221208182356.0c06d5ce@kernel.org> (raw)
In-Reply-To: <202212081947418573438@zte.com.cn>
On Thu, 8 Dec 2022 19:47:41 +0800 (CST) yang.yang29@zte.com.cn wrote:
> Subject: [PATCH linux-next] ethtool: use strscpy() to instead of strncpy()
Also net-next, linux-next is an integration tree, not a development
tree. It does not accept patches.
prev parent reply other threads:[~2022-12-09 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:47 [PATCH linux-next] ethtool: use strscpy() to instead of strncpy() yang.yang29
2022-12-08 13:18 ` Michal Kubecek
2022-12-09 2:23 ` Jakub Kicinski [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=20221208182356.0c06d5ce@kernel.org \
--to=kuba@kernel.org \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=xu.panda@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=yisen.zhuang@huawei.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).