From: patchwork-bot+linux-remoteproc@kernel.org
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 1/2] remoteproc: remoteproc_core: Use 'gnu_printf' format notation
Date: Wed, 15 Jul 2020 19:40:02 +0000 [thread overview]
Message-ID: <159484200274.30575.12937428171208697619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200715123551.4011154-1-lee.jones@linaro.org>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next).
On Wed, 15 Jul 2020 13:35:50 +0100 you wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/remoteproc/remoteproc_core.c: In function ‘rproc_find_carveout_by_name’:
> drivers/remoteproc/remoteproc_core.c:257:2: warning: function ‘rproc_find_carveout_by_name’ might be a candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format]
> 257 | vsnprintf(_name, sizeof(_name), name, args);
> | ^~~~~~~~~
> drivers/remoteproc/remoteproc_core.c: In function ‘rproc_mem_entry_init’:
> drivers/remoteproc/remoteproc_core.c:993:2: warning: function ‘rproc_mem_entry_init’ might be a candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format]
> 993 | vsnprintf(mem->name, sizeof(mem->name), name, args);
> | ^~~~~~~~~
> drivers/remoteproc/remoteproc_core.c: In function ‘rproc_of_resm_mem_entry_init’:
> drivers/remoteproc/remoteproc_core.c:1029:2: warning: function ‘rproc_of_resm_mem_entry_init’ might be a candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format]
> 1029 | vsnprintf(mem->name, sizeof(mem->name), name, args);
> | ^~~~~~~~~
>
> [...]
Here is a summary with links:
- [1/2] remoteproc: remoteproc_core: Use 'gnu_printf' format notation
https://git.kernel.org/andersson/remoteproc/c/7e05c8de132308da0c2a5b17842b808d99a00ca8
- [2/2] remoteproc: qcom_sysmon: Solve function header bitrot issues
https://git.kernel.org/andersson/remoteproc/c/5b435ca38b2ce785b60b4d3c230f0a21121d6728
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
prev parent reply other threads:[~2020-07-15 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:35 [PATCH 1/2] remoteproc: remoteproc_core: Use 'gnu_printf' format notation Lee Jones
2020-07-15 12:35 ` [PATCH 2/2] remoteproc: qcom_sysmon: Solve function header bitrot issues Lee Jones
2020-07-15 19:21 ` Bjorn Andersson
2020-07-15 19:40 ` patchwork-bot+linux-remoteproc [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=159484200274.30575.12937428171208697619.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-remoteproc@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).