From: patchwork-bot+linux-amlogic@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] pwm: meson: remove redundant assignment to variable fin_freq
Date: Thu, 16 Apr 2020 16:08:01 +0000 [thread overview]
Message-ID: <158705328158.8629.3396382198019517190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200402110857.509844-1-colin.king@canonical.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Thu, 2 Apr 2020 12:08:57 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The variable fin_freq is being initialized with a value that is never
> read and it is being updated later with a new value. The initialization
> is redundant and can be removed.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>
> [...]
Here is a summary with links:
- pwm: meson: remove redundant assignment to variable fin_freq
https://git.kernel.org/khilman/linux-amlogic/c/437fb760d046340d0dee3b4307e1cf4578fd8ca8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-04-16 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:08 [PATCH] pwm: meson: remove redundant assignment to variable fin_freq Colin King
2020-04-02 11:08 ` Colin King
2020-04-02 11:08 ` Colin King
2020-04-02 11:08 ` Colin King
2020-04-02 14:15 ` Uwe Kleine-König
2020-04-02 14:15 ` Uwe Kleine-König
2020-04-02 14:15 ` Uwe Kleine-König
2020-04-02 14:15 ` Uwe Kleine-König
2020-04-03 19:43 ` Thierry Reding
2020-04-03 19:43 ` Thierry Reding
2020-04-03 19:43 ` Thierry Reding
2020-04-03 19:43 ` Thierry Reding
2020-04-16 16:08 ` patchwork-bot+linux-amlogic [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=158705328158.8629.3396382198019517190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=colin.king@canonical.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
/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.