From: patchwork-bot+bluetooth@kernel.org
To: Justin Stitt <justinstitt@google.com>
Cc: isdn@linux-pingi.de, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, kees@kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: replace deprecated strncpy with strscpy_pad
Date: Tue, 10 Sep 2024 15:00:32 +0000 [thread overview]
Message-ID: <172598043203.283578.7669553872558102167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240905-strncpy-net-bluetooth-cmtp-capi-c-v1-1-c2d49caa2d36@google.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 05 Sep 2024 15:54:40 -0700 you wrote:
> strncpy() is deprecated for use on NUL-terminated destination strings [0]
> and as such we should prefer more robust and less ambiguous string interfaces.
>
> The CAPI (part II) [1] states that the manufacturer id should be a
> "zero-terminated ASCII string" and should "always [be] zero-terminated."
>
> Much the same for the serial number: "The serial number, a seven-digit
> number coded as a zero-terminated ASCII string".
>
> [...]
Here is the summary with links:
- Bluetooth: replace deprecated strncpy with strscpy_pad
https://git.kernel.org/bluetooth/bluetooth-next/c/278dcc36b992
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:[~2024-09-10 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 22:54 [PATCH] Bluetooth: replace deprecated strncpy with strscpy_pad Justin Stitt
2024-09-10 15:00 ` patchwork-bot+bluetooth [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=172598043203.283578.7669553872558102167.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=isdn@linux-pingi.de \
--cc=johan.hedberg@gmail.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).