public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com>
Cc: Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Boris Brezillon <bbrezillon@kernel.org>,
	Yixun Lan <yixun.lan@amlogic.com>, Lucas Stach <dev@lynxeye.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Stefan Agner <stefan@agner.ch>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	"Bean Huo (beanhuo)" <beanhuo@micron.com>,
	Paul Cercueil <paul@crapouillou.net>,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	Chuanhong Guo <gch981213@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/12] Introduce generic ONFI support
Date: Thu, 27 Jun 2019 16:49:14 +0200	[thread overview]
Message-ID: <20190627164914.1cae84ff@xps13> (raw)
In-Reply-To: <MN2PR08MB59514E77250C3F0DA76D4801B8140@MN2PR08MB5951.namprd08.prod.outlook.com>

Hi Shivamurthy,

"Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com> wrote on
Mon, 3 Jun 2019 12:43:20 +0000:

> Current support to ONFI parameter page is only for raw NAND, this patch
> series turn ONFI support into generic. So that, other NAND devices like
> SPI NAND can use this.
> 
> There are five parts in this series.
> 1. Prepare for turning ONFI into generic
> 2. Turn ONFI into generic, which can be used by SPI NANDs later
> 3. Turn SPI NAND core to use parameter page
> 4. Redesign Micron SPI NAND driver implementation
> 5. Support for new Micron SPI NAND devices
> 

I am very sorry for the delay, I will have a deep look at your series
very soon.

> Changes in V3
> -------------
> 
> * Rebased to nand/next
> * Split the patches as per suggestion
> * Addressed the comments
> * Some fixes which I missed in last version

As a simple note, please mind that "addressed the comments" is way too
generic. "Some fixes" as well. I have plenty of series to follow, you
need to do very careful when you write this changelog, it is important
for me.

Also, for the next series you submit, please use a threaded logic where
all patches are answers to the cover letter (this way it appears as a
thread and it is considered as one series by patchwork.

Thanks,
Miquèl

      reply	other threads:[~2019-06-27 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 12:43 [PATCH v3 00/12] Introduce generic ONFI support Shivamurthy Shastri (sshivamurthy)
2019-06-27 14:49 ` Miquel Raynal [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=20190627164914.1cae84ff@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=anders.roxell@linaro.org \
    --cc=bbrezillon@kernel.org \
    --cc=beanhuo@micron.com \
    --cc=computersforpeace@gmail.com \
    --cc=dev@lynxeye.de \
    --cc=dwmw2@infradead.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=gch981213@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marek.vasut@gmail.com \
    --cc=paul@crapouillou.net \
    --cc=richard@nod.at \
    --cc=sshivamurthy@micron.com \
    --cc=stefan@agner.ch \
    --cc=vigneshr@ti.com \
    --cc=yixun.lan@amlogic.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