From: Richard Weinberger <richard@nod.at>
To: Boris Brezillon <boris.brezillon@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>
Cc: Harvey Hunt <harvey.hunt@imgtec.com>,
IMG-MIPSLinuxKerneldevelopers@imgtec.com,
Alex Smith <alex.smith@imgtec.com>,
Alex Smith <alex@alex-smith.me.uk>,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
David Woodhouse <dwmw2@infradead.org>,
Niklas Cassel <niklas.cassel@axis.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7] mtd: nand: increase ready wait timeout and report timeouts
Date: Fri, 26 Feb 2016 00:27:06 +0100 [thread overview]
Message-ID: <56CF8DCA.7010606@nod.at> (raw)
In-Reply-To: <20160226002302.2f56f1a9@bbrezillon>
Am 26.02.2016 um 00:23 schrieb Boris Brezillon:
>> Regardless, this timeout loop is wrong. Shouldn't it have something like
>> the following?
>>
>> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
>> index f2c8ff398d6c..596a9b0503da 100644
>> --- a/drivers/mtd/nand/nand_base.c
>> +++ b/drivers/mtd/nand/nand_base.c
>> @@ -566,8 +566,8 @@ void nand_wait_ready(struct mtd_info *mtd)
>> cond_resched();
>> } while (time_before(jiffies, timeo));
>>
>> - pr_warn_ratelimited(
>> - "timeout while waiting for chip to become ready\n");
>> + if (!chip->dev_ready(mtd))
>> + pr_warn_ratelimited("timeout while waiting for chip to become ready\n");
>> out:
>> led_trigger_event(nand_led_trigger, LED_OFF);
>> }
>
> Looks good to me.
>
> If you post the patch, you can add
>
> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Same here.
Reviewed-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
next prev parent reply other threads:[~2016-02-25 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 13:52 [PATCH v7] mtd: nand: increase ready wait timeout and report timeouts Harvey Hunt
2015-10-26 20:05 ` Brian Norris
2016-02-25 22:54 ` Richard Weinberger
2016-02-25 23:14 ` Brian Norris
2016-02-25 23:23 ` Boris Brezillon
2016-02-25 23:27 ` Richard Weinberger [this message]
2016-02-26 13:45 ` Harvey Hunt
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=56CF8DCA.7010606@nod.at \
--to=richard@nod.at \
--cc=IMG-MIPSLinuxKerneldevelopers@imgtec.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=alex.smith@imgtec.com \
--cc=alex@alex-smith.me.uk \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=harvey.hunt@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=niklas.cassel@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.