From: Nick Desaulniers <ndesaulniers@google.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v2] mtd: onenand_base: Adjust indentation in onenand_read_ops_nolock
Date: Mon, 9 Dec 2019 13:18:29 -0800 [thread overview]
Message-ID: <CAKwvOd=GYWaoxQg_xH-gOHfqKeTZ_qaw35ucjFxcjd69AK+pyw@mail.gmail.com> (raw)
In-Reply-To: <20191209210328.18866-1-natechancellor@gmail.com>
On Mon, Dec 9, 2019 at 1:04 PM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> Clang warns:
>
> ../drivers/mtd/nand/onenand/onenand_base.c:1269:3: warning: misleading
> indentation; statement is not part of the previous 'if'
> [-Wmisleading-indentation]
> while (!ret) {
> ^
> ../drivers/mtd/nand/onenand/onenand_base.c:1266:2: note: previous
> statement is here
> if (column + thislen > writesize)
> ^
> 1 warning generated.
>
> This warning occurs because there is a space before the tab of the while
> loop. There are spaces at the beginning of a lot of the lines in this
> block, remove them so that the indentation is consistent with the Linux
> kernel coding style and clang no longer warns.
>
> Fixes: a8de85d55700 ("[MTD] OneNAND: Implement read-while-load")
> Link: https://github.com/ClangBuiltLinux/linux/issues/794
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>
> v1 -> v2:
>
> * Clean up the block before the one that warns, which was added as part
> of the fixes commit (Nick).
>
> drivers/mtd/nand/onenand/onenand_base.c | 80 ++++++++++++-------------
> 1 file changed, 40 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/mtd/nand/onenand/onenand_base.c b/drivers/mtd/nand/onenand/onenand_base.c
> index 77bd32a683e1..13c69eb021a6 100644
> --- a/drivers/mtd/nand/onenand/onenand_base.c
> +++ b/drivers/mtd/nand/onenand/onenand_base.c
> @@ -1248,44 +1248,44 @@ static int onenand_read_ops_nolock(struct mtd_info *mtd, loff_t from,
>
> stats = mtd->ecc_stats;
>
> - /* Read-while-load method */
> + /* Read-while-load method */
>
> - /* Do first load to bufferRAM */
> - if (read < len) {
> - if (!onenand_check_bufferram(mtd, from)) {
> + /* Do first load to bufferRAM */
> + if (read < len) {
> + if (!onenand_check_bufferram(mtd, from)) {
> this->command(mtd, ONENAND_CMD_READ, from, writesize);
> - ret = this->wait(mtd, FL_READING);
> - onenand_update_bufferram(mtd, from, !ret);
> + ret = this->wait(mtd, FL_READING);
> + onenand_update_bufferram(mtd, from, !ret);
> if (mtd_is_eccerr(ret))
> ret = 0;
> - }
> - }
> + }
> + }
>
> thislen = min_t(int, writesize, len - read);
> column = from & (writesize - 1);
> if (column + thislen > writesize)
> thislen = writesize - column;
>
> - while (!ret) {
> - /* If there is more to load then start next load */
> - from += thislen;
> - if (read + thislen < len) {
> + while (!ret) {
> + /* If there is more to load then start next load */
> + from += thislen;
> + if (read + thislen < len) {
> this->command(mtd, ONENAND_CMD_READ, from, writesize);
> - /*
> - * Chip boundary handling in DDP
> - * Now we issued chip 1 read and pointed chip 1
> + /*
> + * Chip boundary handling in DDP
> + * Now we issued chip 1 read and pointed chip 1
> * bufferram so we have to point chip 0 bufferram.
> - */
> - if (ONENAND_IS_DDP(this) &&
> - unlikely(from == (this->chipsize >> 1))) {
> - this->write_word(ONENAND_DDP_CHIP0, this->base + ONENAND_REG_START_ADDRESS2);
> - boundary = 1;
> - } else
> - boundary = 0;
> - ONENAND_SET_PREV_BUFFERRAM(this);
> - }
> - /* While load is going, read from last bufferRAM */
> - this->read_bufferram(mtd, ONENAND_DATARAM, buf, column, thislen);
> + */
> + if (ONENAND_IS_DDP(this) &&
> + unlikely(from == (this->chipsize >> 1))) {
> + this->write_word(ONENAND_DDP_CHIP0, this->base + ONENAND_REG_START_ADDRESS2);
> + boundary = 1;
> + } else
> + boundary = 0;
> + ONENAND_SET_PREV_BUFFERRAM(this);
> + }
> + /* While load is going, read from last bufferRAM */
> + this->read_bufferram(mtd, ONENAND_DATARAM, buf, column, thislen);
>
> /* Read oob area if needed */
> if (oobbuf) {
> @@ -1302,23 +1302,23 @@ static int onenand_read_ops_nolock(struct mtd_info *mtd, loff_t from,
> }
>
> /* See if we are done */
With this applied, I see a missed instance right here ^ (L1304).
In vim:
^ \t
In my .vimrc, I set:
https://github.com/nickdesaulniers/dotfiles/blob/37359525f5a403b4ed2d3f9d1bbbee2da8ec8115/.vimrc#L35-L41
to make tabs glaringly visible.
> - read += thislen;
> - if (read == len)
> - break;
> - /* Set up for next read from bufferRAM */
> - if (unlikely(boundary))
> - this->write_word(ONENAND_DDP_CHIP1, this->base + ONENAND_REG_START_ADDRESS2);
> - ONENAND_SET_NEXT_BUFFERRAM(this);
> - buf += thislen;
> + read += thislen;
> + if (read == len)
> + break;
> + /* Set up for next read from bufferRAM */
> + if (unlikely(boundary))
> + this->write_word(ONENAND_DDP_CHIP1, this->base + ONENAND_REG_START_ADDRESS2);
> + ONENAND_SET_NEXT_BUFFERRAM(this);
> + buf += thislen;
> thislen = min_t(int, writesize, len - read);
> - column = 0;
> - cond_resched();
> - /* Now wait for load */
> - ret = this->wait(mtd, FL_READING);
> - onenand_update_bufferram(mtd, from, !ret);
> + column = 0;
> + cond_resched();
> + /* Now wait for load */
> + ret = this->wait(mtd, FL_READING);
> + onenand_update_bufferram(mtd, from, !ret);
> if (mtd_is_eccerr(ret))
> ret = 0;
> - }
> + }
>
> /*
> * Return success, if no ECC failures, else -EBADMSG
> --
> 2.24.0
>
> --
> You received this message because you are subscribed to the Google Groups "Clang Built Linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to clang-built-linux+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/clang-built-linux/20191209210328.18866-1-natechancellor%40gmail.com.
--
Thanks,
~Nick Desaulniers
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-12-09 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:50 [PATCH] mtd: onenand_base: Adjust indentation in onenand_read_ops_nolock Nathan Chancellor
2019-12-09 20:58 ` Nick Desaulniers
2019-12-09 21:03 ` [PATCH v2] " Nathan Chancellor
2019-12-09 21:18 ` Nick Desaulniers [this message]
2019-12-09 21:44 ` [PATCH v3] " Nathan Chancellor
2020-01-14 17:07 ` 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='CAKwvOd=GYWaoxQg_xH-gOHfqKeTZ_qaw35ucjFxcjd69AK+pyw@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=natechancellor@gmail.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).