[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20201210182150.GE1578121@piout.net>
Date: Thu, 10 Dec 2020 19:21:50 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: linux-mmc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Colin Ian King <colin.king@...onical.com>
Subject: Re: [PATCH] mmc: atmel-mci: Reduce scope for the variable “slot” in
atmci_request_end()
On 10/12/2020 18:23:05+0100, Markus Elfring wrote:
> >> Can the extra null pointer initialisation trigger a source code analysis warning
> >> like “Addresses-Coverity: ("Unused value")” for this function implementation?
> >>
> >
> > Did you check, does it? It doesn't.
> >
> > Are you wasting maintainer and reviewer's time? Yes you are.
>
> How do you think about a patch like “staging: speakup: remove redundant initialization
> of pointer p_key” for comparison?
> https://lore.kernel.org/patchwork/patch/1199128/
> https://lore.kernel.org/driverdev-devel/20200223153954.420731-1-colin.king@canonical.com/
>
> Would you tolerate to omit the initialisation for the variable “slot”?
>
If you were able to provide one good technical reason.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists