All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: linux-kernel@vger.kernel.org, krzysztof.kozlowski@linaro.org,
	agross@kernel.org, sboyd@kernel.org, mturquette@baylibre.com,
	linux-clk@vger.kernel.org, mathieu.poirier@linaro.org,
	linux-remoteproc@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH 4/8] rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
Date: Mon, 18 Jul 2022 17:59:06 -0500	[thread overview]
Message-ID: <165817634384.1905814.11996354687051888253.b4-ty@linaro.org> (raw)
In-Reply-To: <20220501103520.111561-4-krzysztof.kozlowski@linaro.org>

On Sun, 1 May 2022 12:35:16 +0200, Krzysztof Kozlowski wrote:
> The use of strncpy() is considered deprecated for NUL-terminated
> strings[1]. Replace strncpy() with strscpy_pad(), to keep existing
> pad-behavior of strncpy, similarly to commit 08de420a8014 ("rpmsg:
> glink: Replace strncpy() with strscpy_pad()").  This fixes W=1 warning:
> 
>   In function ‘qcom_glink_rx_close’,
>     inlined from ‘qcom_glink_work’ at ../drivers/rpmsg/qcom_glink_native.c:1638:4:
>   drivers/rpmsg/qcom_glink_native.c:1549:17: warning: ‘strncpy’ specified bound 32 equals destination size [-Wstringop-truncation]
>    1549 |                 strncpy(chinfo.name, channel->name, sizeof(chinfo.name));
> 
> [...]

Applied, thanks!

[4/8] rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
      commit: 766279a8f85df32345dbda03b102ca1ee3d5ddea

Best regards,
-- 
Bjorn Andersson <bjorn.andersson@linaro.org>

  reply	other threads:[~2022-07-18 22:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 10:35 [PATCH 1/8] clk: qcom: alpha-pll: correct kerneldoc Krzysztof Kozlowski
2022-05-01 10:35 ` [PATCH 2/8] firmware: qcom_scm-legacy: " Krzysztof Kozlowski
2022-05-19  0:03   ` Stephen Boyd
2022-05-19  7:20     ` Krzysztof Kozlowski
2022-05-01 10:35 ` [PATCH 3/8] remoteproc: qcom: " Krzysztof Kozlowski
2022-05-19  0:05   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 4/8] rpmsg: qcom: glink: replace strncpy() with strscpy_pad() Krzysztof Kozlowski
2022-07-18 22:59   ` Bjorn Andersson [this message]
2022-05-01 10:35 ` [PATCH 5/8] rpmsg: qcom: glink: remove unused name Krzysztof Kozlowski
2022-05-19  0:09   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 6/8] rpmsg: qcom: correct kerneldoc Krzysztof Kozlowski
2022-05-19  0:11   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 7/8] soc: qcom: cmd-db: replace strncpy() with strscpy_pad() Krzysztof Kozlowski
2022-05-19  0:12   ` Stephen Boyd
2022-05-01 10:35 ` [PATCH 8/8] soc: qcom: correct kerneldoc Krzysztof Kozlowski
2022-05-19  0:13   ` Stephen Boyd
2022-05-17 16:46 ` [PATCH 1/8] clk: qcom: alpha-pll: " Krzysztof Kozlowski
2022-05-19  0:14   ` Stephen Boyd
2022-05-19  7:23     ` Krzysztof Kozlowski
2022-05-19  0:02 ` Stephen Boyd
2022-05-19  7:20   ` Krzysztof Kozlowski
2022-05-19  4:30 ` Vladimir Zapolskiy
2022-05-19  7:23   ` Krzysztof Kozlowski

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=165817634384.1905814.11996354687051888253.b4-ty@linaro.org \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 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.