From: Felix Kuehling <felix.kuehling@amd.com>
To: Philip Yang <Philip.Yang@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/amdkfd: Add format attribute to kfd_smi_event_add
Date: Fri, 4 Mar 2022 11:32:10 -0500 [thread overview]
Message-ID: <93954fba-4e96-25f2-2523-e62381ed130b@amd.com> (raw)
In-Reply-To: <20220304144811.17451-1-Philip.Yang@amd.com>
Am 2022-03-04 um 09:48 schrieb Philip Yang:
> To enable compiler type-checked against the format string in callers.
>
> All warnings (new ones prefixed by >>):
>
>>> warning: function 'kfd_smi_event_add' might be a candidate for
> 'gnu_printf' format attribute [-Wsuggest-attribute=format]
>
> Fixes: 67e874c2fa ("drm/amdkfd: Add SMI add event helper")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Philip Yang <Philip.Yang@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c b/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> index bba8d9692a4c..02b6b26ee8f3 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c
> @@ -176,6 +176,7 @@ static void add_event_to_kfifo(struct kfd_dev *dev, unsigned int smi_event,
> rcu_read_unlock();
> }
>
> +__attribute__ ((format (printf, 3, 4)))
I see that there is a shortcut for this defined in
include/linux/compiler_attributes.h. It's just
__printf(3, 4)
With that fixed, the patch is
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
> static void kfd_smi_event_add(struct kfd_dev *dev, unsigned int event,
> char *fmt, ...)
> {
prev parent reply other threads:[~2022-03-04 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 14:48 [PATCH 1/1] drm/amdkfd: Add format attribute to kfd_smi_event_add Philip Yang
2022-03-04 16:32 ` Felix Kuehling [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=93954fba-4e96-25f2-2523-e62381ed130b@amd.com \
--to=felix.kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=amd-gfx@lists.freedesktop.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