From: "Petr Mladek via lists.elisa.tech" <pmladek=suse.com@lists.elisa.tech>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
kernel-janitors@vger.kernel.org, linux-safety@lists.elisa.tech
Subject: Re: [linux-safety] [PATCH] printk: remove obsolete dead assignment
Date: Tue, 8 Dec 2020 17:00:31 +0100 [thread overview]
Message-ID: <X8+jHx7sRlroUM8u@alley> (raw)
In-Reply-To: <20201130124915.7573-1-lukas.bulwahn@gmail.com>
On Mon 2020-11-30 13:49:15, Lukas Bulwahn wrote:
> Commit 849f3127bb46 ("switch /dev/kmsg to ->write_iter()") refactored
> devkmsg_write() and left over a dead assignment on the variable 'len'.
>
> Hence, make clang-analyzer warns:
>
> kernel/printk/printk.c:744:4: warning: Value stored to 'len' is never read
> [clang-analyzer-deadcode.DeadStores]
> len -= endp - line;
> ^
>
> Simply remove this obsolete dead assignment here.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
The patch is committed in printk/linux.git, branch for-5.11.
Best Regards,
Petr
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#216): https://lists.elisa.tech/g/linux-safety/message/216
Mute This Topic: https://lists.elisa.tech/mt/78607109/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2020-12-08 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 12:49 [linux-safety] [PATCH] printk: remove obsolete dead assignment Lukas Bulwahn
2020-11-30 15:37 ` Petr Mladek via lists.elisa.tech
2020-11-30 15:53 ` Sergey Senozhatsky
2020-12-08 16:00 ` Petr Mladek via lists.elisa.tech [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=X8+jHx7sRlroUM8u@alley \
--to=pmladek=suse.com@lists.elisa.tech \
--cc=clang-built-linux@googlegroups.com \
--cc=john.ogness@linutronix.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@gmail.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).