From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
matthias.bgg@gmail.com, robh@kernel.org,
linux-mtd@lists.infradead.org, xiaolei.li@mediatek.com,
daniel.thompson@linaro.org, erin.lo@mediatek.com,
linux-mediatek@lists.infradead.org
Subject: Re: [RFCv2 0/2] MTK Smart Device Gen1 NAND Driver
Date: Tue, 22 Mar 2016 10:08:00 -0400 [thread overview]
Message-ID: <56F151C0.4090601@linaro.org> (raw)
In-Reply-To: <20160322144728.0a1d8ecf@bbrezillon>
On 03/22/2016 09:47 AM, Boris Brezillon wrote:
> You can drop the RFC prefix for your next version (the driver does not
> look bad, and it's definitely not an RFC ;)). Just prefix your patches
> with "PATCH vX".
sure, sounds good to me. and thanks for the quick response!.
we will incorporate any changes into v3 (unless there are just a few of them
will probably do v3 after ELC - I'll be at your talk btw)
prev parent reply other threads:[~2016-03-22 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 13:32 [RFCv2 0/2] MTK Smart Device Gen1 NAND Driver Jorge Ramirez-Ortiz
2016-03-22 13:32 ` [RFCv2: PATCH 1/2] mtd: mediatek: device tree docs for MTK Smart Device Gen1 NAND Jorge Ramirez-Ortiz
2016-03-22 13:52 ` Boris Brezillon
2016-03-26 18:38 ` Jorge Ramirez-Ortiz
2016-03-29 7:58 ` Boris Brezillon
2016-03-31 12:41 ` Jorge Ramirez-Ortiz
2016-03-22 13:32 ` [RFCv2: PATCH 2/2] mtd: mediatek: driver " Jorge Ramirez-Ortiz
2016-03-22 16:58 ` Boris Brezillon
2016-03-22 23:43 ` Jorge Ramirez-Ortiz
2016-03-23 8:41 ` Boris Brezillon
2016-03-23 12:44 ` Jorge Ramirez-Ortiz
2016-03-23 0:29 ` Jorge Ramirez-Ortiz
2016-03-23 8:26 ` Boris Brezillon
2016-03-22 13:47 ` [RFCv2 0/2] MTK Smart Device Gen1 NAND Driver Boris Brezillon
2016-03-22 14:08 ` Jorge Ramirez-Ortiz [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=56F151C0.4090601@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dwmw2@infradead.org \
--cc=erin.lo@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=xiaolei.li@mediatek.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).