From: John Hubbard <jhubbard@nvidia.com>
To: Jaroslav Kysela <perex@perex.cz>, linux-sound@vger.kernel.org
Cc: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] selftests/alsa: make dump_config_tree() as void function
Date: Mon, 6 May 2024 10:39:42 -0700 [thread overview]
Message-ID: <81d24856-cf09-4376-929c-d0bf7fa8e8ee@nvidia.com> (raw)
In-Reply-To: <20240506075419.301780-1-perex@perex.cz>
On 5/6/24 12:54 AM, Jaroslav Kysela wrote:
> dump_config_tree() is declared to return an int, but the compiler cannot
> prove that it always returns any value at all. This leads to a clang
> warning, when building via:
>
> make LLVM=1 -C tools/testing/selftests
>
> Suggested-by: John Hubbard <jhubbard@nvidia.com>
> Cc: Mark Brown <broonie@kernel.org>
> Signed-off-by: Jaroslav Kysela <perex@perex.cz>
> ---
> tools/testing/selftests/alsa/conf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/alsa/conf.c b/tools/testing/selftests/alsa/conf.c
> index 89e3656a042d..e2b3a5810f47 100644
> --- a/tools/testing/selftests/alsa/conf.c
> +++ b/tools/testing/selftests/alsa/conf.c
> @@ -105,7 +105,7 @@ static struct card_cfg_data *conf_data_by_card(int card, bool msg)
> return NULL;
> }
>
> -static int dump_config_tree(snd_config_t *top)
> +static void dump_config_tree(snd_config_t *top)
OK, looks good. :)
> {
> snd_output_t *out;
> int err;
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2024-05-06 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 7:54 [PATCH] selftests/alsa: make dump_config_tree() as void function Jaroslav Kysela
2024-05-06 14:45 ` Mark Brown
2024-05-06 16:15 ` Takashi Iwai
2024-05-06 17:39 ` John Hubbard [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=81d24856-cf09-4376-929c-d0bf7fa8e8ee@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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