linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Richard Weinberger <richard@nod.at>,
	kernel test robot <lkp@intel.com>,
	linux-mtd@lists.infradead.org,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>
Subject: Re: [PATCH] mtd: nand: ecc-hamming: Clarify the logic around rp17
Date: Thu, 29 Oct 2020 11:34:25 +0100	[thread overview]
Message-ID: <20201029113425.26f83231@xps13> (raw)
In-Reply-To: <20201029102705.GR18329@kadam>

Hi Dan,

Dan Carpenter <dan.carpenter@oracle.com> wrote on Thu, 29 Oct 2020
13:27:05 +0300:

> On Thu, Oct 29, 2020 at 09:38:47AM +0100, Miquel Raynal wrote:
> > This code has been written in 2008 and is fine, but in order to keep
> > robots happy, I think it's time to change a little bit this code just
> > to clarify the different possible values of eccsize_mult. Indeed, this
> > variable may only take the value 1 or 2 because step_size, in the case
> > of the software Hamming ECC engine may only be 256 or 512. Depending
> > on the value of eccsize_mult, an extra rp17 variable is set, or not
> > and triggers the following warning:
> > 
> >      smatch warnings:
> >      ecc_sw_hamming_calculate() error: uninitialized symbol 'rp17'.
> > 
> > As highlighted by Dan Carpenter, if the only possible values for
> > eccsize_mult are 1 and 2, then the code is fine, but "it's hard to
> > tell just from looking".
> > 
> > So instead of shifting step_size, let's use a ternary condition to
> > assign to eccsize_mult the only two possible values and clarify the
> > driver's logic.
> > 
> > Now that the situation is clarified for humans, set rp17 to 0 in an
> > else block to keep robots silent as well.  
> 
> Smatch will parse it correctly with just the ternary change but there
> might be other checkers which want the the else statement.  I'm not
> sure.  GCC doesn't seem to warn about uninitialized variables these
> days.

Well, I thought about this after having written the commit log, I
amended the commit to just keep the ternary change and I forgot to drop
this part of the commit log.

So if the change looks good to you I can simply drop the last paragraph
when applying.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-10-29 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  8:38 [PATCH] mtd: nand: ecc-hamming: Clarify the logic around rp17 Miquel Raynal
2020-10-29 10:27 ` Dan Carpenter
2020-10-29 10:34   ` Miquel Raynal [this message]
2020-10-30 17:20     ` Miquel Raynal

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=20201029113425.26f83231@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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 NNTP newsgroup(s).