From: Jens Axboe <axboe@kernel.dk>
To: ndesaulniers@google.com, michalorzel.eng@gmail.com,
trix@redhat.com, nathan@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH RESEND v2 1/5] block/badblocks: Remove redundant assignments
Date: Sat, 23 Apr 2022 07:15:44 -0600 [thread overview]
Message-ID: <165071974452.502130.12676791188164630002.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220423113811.13335-1-michalorzel.eng@gmail.com>
On Sat, 23 Apr 2022 13:38:07 +0200, Michal Orzel wrote:
> Get rid of redundant assignments to a variable sectors from functions
> badblocks_check and badblocks_clear. This variable, that is a function
> parameter, is being assigned a value that is never read until the end of
> function.
>
> Reported by clang-tidy [deadcode.DeadStores]
>
> [...]
Applied, thanks!
[1/5] block/badblocks: Remove redundant assignments
commit: 3de2e5f28cb133f1d9c1b2403079722d0e7b671e
[2/5] block/blk-map: Remove redundant assignment
commit: 7ab89db979017255c2163880de5c63d8c9726aef
[3/5] block/partitions/acorn: Remove redundant assignments
commit: 834726828b47c08e84df02f975e30c5c65bf316b
[4/5] block/partitions/atari: Remove redundant assignment
commit: 87420fa94f6cdd2ae8aa3e1d8602bfa549794fac
[5/5] block/partitions/ldm: Remove redundant assignments
commit: e233fe1aa02815f38588a5a965a197bbcabfb125
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-23 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 11:38 Michal Orzel
2022-04-23 11:38 ` [PATCH RESEND v2 2/5] block/blk-map: Remove redundant assignment Michal Orzel
2022-04-23 11:38 ` [PATCH RESEND v2 3/5] block/partitions/acorn: Remove redundant assignments Michal Orzel
2022-04-23 11:38 ` [PATCH RESEND v2 4/5] block/partitions/atari: Remove redundant assignment Michal Orzel
2022-04-23 11:38 ` [PATCH RESEND v2 5/5] block/partitions/ldm: Remove redundant assignments Michal Orzel
2022-04-23 13:15 ` Jens Axboe [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=165071974452.502130.12676791188164630002.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=michalorzel.eng@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®