public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
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 14:47:28 +0100	[thread overview]
Message-ID: <20160322144728.0a1d8ecf@bbrezillon> (raw)
In-Reply-To: <1458653560-2679-1-git-send-email-jorge.ramirez-ortiz@linaro.org>

Hi Jorge,

On Tue, 22 Mar 2016 09:32:38 -0400
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> wrote:

> Fixes/Changes on v2 relative to: 
> --------------------------------
> 
>   tree		: https://github.com/bbrezillon/linux-0day
>   branch	: nand/ecclayout
>   commit	:
>  		commit eafabf3b93f5ba796081d1beab3b9ed0dea40a9a
> 		Author: Boris Brezillon <boris.brezillon@free-electrons.com>
> 		Date:	Thu Feb 4 10:16:18 2016 +0100
> 
> 		mtd: kill the nand_ecclayout struct
> 
>   RFC v2:

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".

Best Regards,

Boris

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2016-03-22 13:47 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 ` Boris Brezillon [this message]
2016-03-22 14:08   ` [RFCv2 0/2] MTK Smart Device Gen1 NAND Driver Jorge Ramirez-Ortiz

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=20160322144728.0a1d8ecf@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=daniel.thompson@linaro.org \
    --cc=dwmw2@infradead.org \
    --cc=erin.lo@mediatek.com \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --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