From: patchwork-bot+netdevbpf@kernel.org
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: yisen.zhuang@huawei.com, salil.mehta@huawei.com,
davem@davemloft.net, kuba@kernel.org, huangguangbin2@huawei.com,
moyufeng@huawei.com, tanhuazhong@huawei.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: hns3: fix different snprintf() limit
Date: Mon, 21 Jun 2021 19:20:04 +0000 [thread overview]
Message-ID: <162430320494.6988.10698969626781207552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YM31etbBvDRf+bgS@mwanda>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 19 Jun 2021 16:47:38 +0300 you wrote:
> This patch doesn't affect runtime at all, it's just a correctness issue.
>
> The ptp->info.name[] buffer has 16 characters but the snprintf() limit
> was capped at 32 characters. Fortunately, HCLGE_DRIVER_NAME is "hclge"
> which isn't close to 16 characters so we're fine.
>
> Fixes: 0bf5eb788512 ("net: hns3: add support for PTP")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: hns3: fix different snprintf() limit
https://git.kernel.org/netdev/net-next/c/faebad853455
- [net-next,2/2] net: hns3: fix a double shift bug
https://git.kernel.org/netdev/net-next/c/956c3ae411b2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-21 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 13:47 [PATCH net-next 1/2] net: hns3: fix different snprintf() limit Dan Carpenter
2021-06-19 13:49 ` [PATCH net-next 2/2] net: hns3: fix a double shift bug Dan Carpenter
2021-06-21 19:20 ` patchwork-bot+netdevbpf [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=162430320494.6988.10698969626781207552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@huawei.com \
--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).