Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alexander Heinrich <hallo@alexanderheinrich.de>
Cc: broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
	shuah@kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] kselftest/alsa: Fix -Wformat compiler warnings
Date: Fri, 24 Mar 2023 10:43:38 +0100	[thread overview]
Message-ID: <87sfdu5vsl.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230324092806.363253-1-hallo@alexanderheinrich.de>

On Fri, 24 Mar 2023 10:28:06 +0100,
Alexander Heinrich wrote:
> 
> I noticed some -Wformat compiler warnings in pcm-test.c while building
> kselftest, fix them by using the same types for format specifier and arguments.
> 
> Signed-off-by: Alexander Heinrich <hallo@alexanderheinrich.de>

Those variables (rates, channels, etc) should be rather int instead of
long, as these are not 64bit parameters on 32bit archs.
On top of that, the whole '%l' prefix and cast should be dropped.

The only concern is the string to int conversion, and this should be
checked carefully, but other than that, it must be straightforward.

Care to work on that way?


thanks,

Takashi

> ---
>  tools/testing/selftests/alsa/pcm-test.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/tools/testing/selftests/alsa/pcm-test.c b/tools/testing/selftests/alsa/pcm-test.c
> index 58b525a4a32c..44fc5f826ab5 100644
> --- a/tools/testing/selftests/alsa/pcm-test.c
> +++ b/tools/testing/selftests/alsa/pcm-test.c
> @@ -371,7 +371,7 @@ static void test_pcm_time(struct pcm_data *data, enum test_class class,
>  		goto __close;
>  	}
>  	if (rrate != rate) {
> -		snprintf(msg, sizeof(msg), "rate mismatch %ld != %ld", rate, rrate);
> +		snprintf(msg, sizeof(msg), "rate mismatch %ld != %d", rate, rrate);
>  		goto __close;
>  	}
>  	rperiod_size = period_size;
> @@ -437,24 +437,24 @@ static void test_pcm_time(struct pcm_data *data, enum test_class class,
>  			frames = snd_pcm_writei(handle, samples, rate);
>  			if (frames < 0) {
>  				snprintf(msg, sizeof(msg),
> -					 "Write failed: expected %d, wrote %li", rate, frames);
> +					 "Write failed: expected %ld, wrote %li", rate, frames);
>  				goto __close;
>  			}
>  			if (frames < rate) {
>  				snprintf(msg, sizeof(msg),
> -					 "expected %d, wrote %li", rate, frames);
> +					 "expected %ld, wrote %li", rate, frames);
>  				goto __close;
>  			}
>  		} else {
>  			frames = snd_pcm_readi(handle, samples, rate);
>  			if (frames < 0) {
>  				snprintf(msg, sizeof(msg),
> -					 "expected %d, wrote %li", rate, frames);
> +					 "expected %ld, wrote %li", rate, frames);
>  				goto __close;
>  			}
>  			if (frames < rate) {
>  				snprintf(msg, sizeof(msg),
> -					 "expected %d, wrote %li", rate, frames);
> +					 "expected %ld, wrote %li", rate, frames);
>  				goto __close;
>  			}
>  		}
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-03-24  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  9:28 [PATCH] kselftest/alsa: Fix -Wformat compiler warnings Alexander Heinrich
2023-03-24  9:43 ` Takashi Iwai [this message]
2023-03-24  9:44   ` Takashi Iwai

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=87sfdu5vsl.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=hallo@alexanderheinrich.de \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=shuah@kernel.org \
    --cc=tiwai@suse.com \
    /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