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 v2] mtd: spi-nor: Refactor spi_nor_read_id()
Date: Mon, 2 Mar 2020 18:11:41 +0000 [thread overview]
Message-ID: <11395630.65iIH9RknS@localhost.localdomain> (raw)
In-Reply-To: <20200223173713.2981-1-j.neuschaefer@gmx.net>
On Sunday, February 23, 2020 7:37:13 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).
> Instead, use `i` for the loop counter, and `ret` for the return value.
> - Don't use tabs between type and name in variable declarations,
> for consistency with other functions in spi-nor.c.
> - Rewrite nested `if`s as `if (a && b)`.
> - Remove `info` variable, and use spi_nor_ids[i] directly.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
>
> v2:
> - As suggested by Tudor Ambarus:
> - rename tmp to ret
> - remove tabs between variable type and name
> - remove `info` variable
>
> v1:
> - https://lore.kernel.org/lkml/20200218151034.24744-1-j.neuschaefer@gmx.net/
> ---
> drivers/mtd/spi-nor/spi-nor.c | 25 +++++++++++--------------
> 1 file changed, 11 insertions(+), 14 deletions(-)
>
Changed i's type from int to unsigned int, reordered local variables and
applied to spi-nor/next. Thanks,
ta
prev parent reply other threads:[~2020-03-02 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 17:37 [PATCH v2] mtd: spi-nor: Refactor spi_nor_read_id() Jonathan Neuschäfer
2020-03-02 18:11 ` Tudor.Ambarus [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=11395630.65iIH9RknS@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