From: Takashi Iwai <tiwai@suse.de>
To: Tom Rix <trix@redhat.com>
Cc: tiwai@suse.com, nathan@kernel.org, ndesaulniers@google.com,
wangjianli@cdjrlc.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] ALSA: remove unused loop_count variable
Date: Wed, 29 Mar 2023 14:41:30 +0200 [thread overview]
Message-ID: <87tty3ohl1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230326205712.1358918-1-trix@redhat.com>
On Sun, 26 Mar 2023 22:57:12 +0200,
Tom Rix wrote:
>
> clang with W=1 reports
> sound/pci/asihpi/hpi6000.c:1256:6: error: variable
> 'loop_count' set but not used [-Werror,-Wunused-but-set-variable]
> u32 loop_count = 0;
> ^
> This variable is not used so remove it.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
Applied, thanks.
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Tom Rix <trix@redhat.com>
Cc: perex@perex.cz, tiwai@suse.com, nathan@kernel.org,
ndesaulniers@google.com, wangjianli@cdjrlc.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] ALSA: remove unused loop_count variable
Date: Wed, 29 Mar 2023 14:41:30 +0200 [thread overview]
Message-ID: <87tty3ohl1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230326205712.1358918-1-trix@redhat.com>
On Sun, 26 Mar 2023 22:57:12 +0200,
Tom Rix wrote:
>
> clang with W=1 reports
> sound/pci/asihpi/hpi6000.c:1256:6: error: variable
> 'loop_count' set but not used [-Werror,-Wunused-but-set-variable]
> u32 loop_count = 0;
> ^
> This variable is not used so remove it.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
Applied, thanks.
Takashi
next prev parent reply other threads:[~2023-03-29 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 20:57 [PATCH] ALSA: remove unused loop_count variable Tom Rix
2023-03-29 12:41 ` Takashi Iwai [this message]
2023-03-29 12:41 ` 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=87tty3ohl1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=tiwai@suse.com \
--cc=trix@redhat.com \
--cc=wangjianli@cdjrlc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.