archive mirror
 help / color / mirror / Atom feed
To: Dan Carpenter <>
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: <> (raw)
In-Reply-To: <YM31etbBvDRf+bgS@mwanda>


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->[] 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 <>
> [...]

Here is the summary with links:
  - [net-next,1/2] net: hns3: fix different snprintf() limit
  - [net-next,2/2] net: hns3: fix a double shift bug

You are awesome, thank you!
Deet-doot-dot, I am a bot.

      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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).