From: Takashi Iwai <tiwai@suse.de>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
kernel-janitors@vger.kernel.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ALSA: wavefront: remove redundant assignment to pointer end
Date: Mon, 04 Jul 2022 14:30:17 +0200 [thread overview]
Message-ID: <8735fhys9y.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220629102744.139673-1-colin.i.king@gmail.com>
On Wed, 29 Jun 2022 12:27:43 +0200,
Colin Ian King wrote:
>
> Pointer end is being re-assigned the same value as it was initialized
> with in the previous statement. The re-assignment is redundant and
> can be removed.
>
> Cleans up clang scan-build warning:
> sound/isa/wavefront/wavefront_synth.c:582:17: warning: Value stored
> to 'end' during its initialization is never read
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Thanks, applied now.
Takashi
prev parent reply other threads:[~2022-07-04 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 10:27 [PATCH] ALSA: wavefront: remove redundant assignment to pointer end Colin Ian King
2022-06-29 10:27 ` Colin Ian King
2022-07-04 12:30 ` Takashi Iwai [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=8735fhys9y.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.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