From: <Tudor.Ambarus@microchip.com>
To: <j.neuschaefer@gmx.net>
Cc: <linux-mtd@lists.infradead.org>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: Simplify loop in spi_nor_read_id()
Date: Wed, 19 Feb 2020 08:06:08 +0000 [thread overview]
Message-ID: <5604429.rq6fcmI4QA@localhost.localdomain> (raw)
In-Reply-To: <20200218151034.24744-1-j.neuschaefer@gmx.net>
Hi, Jonathan,
On Tuesday, February 18, 2020 5:10:34 PM EET Jonathan Neuschäfer wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> - Don't use `tmp` for two purposes (return value, loop counter)
> - Name the loop counter `i`, as is convention
> - Return the pointer variable that the if conditions leading up to the
> return statement already operate on, rather than a different
> expression that evaluates to the same pointer
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> drivers/mtd/spi-nor/spi-nor.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 4fc632ec18fe..c491572d5267 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -2711,7 +2711,7 @@ static const struct flash_info spi_nor_ids[] = {
>
> static const struct flash_info *spi_nor_read_id(struct spi_nor *nor)
> {
> - int tmp;
> + int tmp, i;
while cleaning this function, would you rename tmp with ret?
> u8 *id = nor->bouncebuf;
and please drop this tab between u8 and *id
> const struct flash_info *info;
Also, IMO, the definition of variables should be done with the focus of
avoiding stack padding. With this in mind, I would first define the pointers
and then the ints and smaller types. But there are others than prefer defining
the variables in a tree/reverse-tree way, depending of the length of the line.
There's no agreement on this, either way if fine, do as you prefer.
>
> @@ -2732,11 +2732,11 @@ static const struct flash_info
> *spi_nor_read_id(struct spi_nor *nor) return ERR_PTR(tmp);
> }
>
> - for (tmp = 0; tmp < ARRAY_SIZE(spi_nor_ids) - 1; tmp++) {
> - info = &spi_nor_ids[tmp];
> + for (i = 0; i < ARRAY_SIZE(spi_nor_ids) - 1; i++) {
> + info = &spi_nor_ids[i];
> if (info->id_len) {
> if (!memcmp(info->id, id, info->id_len))
> - return &spi_nor_ids[tmp];
> + return info;
Looks good,
Cheers,
ta
next prev parent reply other threads:[~2020-02-19 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:10 [PATCH] mtd: spi-nor: Simplify loop in spi_nor_read_id() Jonathan Neuschäfer
2020-02-19 8:06 ` Tudor.Ambarus [this message]
2020-02-21 16:22 ` Jonathan Neuschäfer
2020-02-21 16:50 ` Tudor.Ambarus
2020-02-22 21:51 ` Jonathan Neuschäfer
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=5604429.rq6fcmI4QA@localhost.localdomain \
--to=tudor.ambarus@microchip.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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