From: Greg KH <gregkh@linuxfoundation.org>
To: Emre Cecanpunar <emreleno@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-tegra@vger.kernel.org,
marvin24@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: nvec: silence macro argument warnings in NVEC_PHD()
Date: Wed, 9 Jul 2025 13:06:01 +0200 [thread overview]
Message-ID: <2025070914-repave-feisty-b44a@gregkh> (raw)
In-Reply-To: <20250704152737.14315-1-emreleno@gmail.com>
On Fri, Jul 04, 2025 at 06:27:37PM +0300, Emre Cecanpunar wrote:
> checkpatch.pl warns that the NVEC_PHD macro defines unused arguments.
> Use (void) casts to prevent unused argument warnings when the macro is disabled.
>
> Signed-off-by: Emre Cecanpunar <emreleno@gmail.com>
> ---
> drivers/staging/nvec/nvec_ps2.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/nvec/nvec_ps2.c b/drivers/staging/nvec/nvec_ps2.c
> index 575233fa1677..38e736b3761e 100644
> --- a/drivers/staging/nvec/nvec_ps2.c
> +++ b/drivers/staging/nvec/nvec_ps2.c
> @@ -28,7 +28,11 @@
> print_hex_dump(KERN_DEBUG, str, DUMP_PREFIX_NONE, \
> 16, 1, buf, len, false)
> #else
> -#define NVEC_PHD(str, buf, len) do { } while (0)
> +#define NVEC_PHD(str, buf, len) do { \
> + (void)(str); \
> + (void)(buf); \
> + (void)(len); \
> +} while (0)
This is really not needed at all, sorry. Especially for a define that
will never even be used. Can you work to remove NVEC_PS2_DEBUG instead,
as that's not a good idea.
thanks,
greg k-h
prev parent reply other threads:[~2025-07-09 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 15:27 [PATCH] staging: nvec: silence macro argument warnings in NVEC_PHD() Emre Cecanpunar
2025-07-09 11:06 ` Greg KH [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=2025070914-repave-feisty-b44a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=emreleno@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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