From: Kyle Roeschley <kyle.roeschley@ni.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: <richard@nod.at>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <beanhuo@micron.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<nathan.sullivan@ni.com>, <xander.huff@ni.com>,
<peterpansjtu@gmail.com>
Subject: Re: [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt()
Date: Fri, 12 Aug 2016 14:47:29 -0500 [thread overview]
Message-ID: <20160812194729.GA16998@senary> (raw)
In-Reply-To: <20160812211503.484e3553@bbrezillon>
Hi Boris,
On Fri, Aug 12, 2016 at 09:15:03PM +0200, Boris Brezillon wrote:
> Hi Kyle,
>
> On Fri, 12 Aug 2016 12:54:49 -0500
> Kyle Roeschley <kyle.roeschley@ni.com> wrote:
>
> > From: Boris Brezillon <boris.brezillon@free-electrons.com>
> >
> > This clarifies the write_bbt() by removing the write label and clarifying
> > the error/exit path.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> Just want to make sure you actually tested those patches, because I
> didn't :).
>
> Can you add your Tested-by on this one and confirm you've tested patch
> 2 as well.
Whoops, I goofed and only tested with both patches applied. Thanks for the
catch. I'll go ahead and test the first alone and submit a v7.
Regards,
--
Kyle Roeschley
Software Engineer
National Instruments
prev parent reply other threads:[~2016-08-12 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:54 [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt() Kyle Roeschley
2016-08-12 17:54 ` [PATCH v6 2/2] mtd: nand_bbt: scan for next free bbt block if writing bbt fails Kyle Roeschley
2016-08-12 19:30 ` kbuild test robot
2016-08-12 19:15 ` [PATCH v6 1/2] mtd: nand_bbt: Move BBT block selection logic out of write_bbt() Boris Brezillon
2016-08-12 19:47 ` Kyle Roeschley [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=20160812194729.GA16998@senary \
--to=kyle.roeschley@ni.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nathan.sullivan@ni.com \
--cc=peterpansjtu@gmail.com \
--cc=richard@nod.at \
--cc=xander.huff@ni.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).