public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maximintegrated.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>,
	Huang Shijie <b32955@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"pekon@ti.com" <pekon@ti.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH v4 4/6] mtd: set ONFI nand's default hooks in nand_set_defaults()
Date: Tue, 20 Aug 2013 09:09:07 +0200	[thread overview]
Message-ID: <2807293.aRGNn81TaS@laclwks004> (raw)
In-Reply-To: <CAN8TOE-LC+p6Vt9GB7kiT-ytqnD2aMJ7sKMwZMEa3QHiKCwhhw@mail.gmail.com>

On Monday 19-August-2013 17:41:17 Brian Norris wrote:
> On Mon, Aug 19, 2013 at 1:06 AM, Brian Foster
> <brian.foster@maximintegrated.com> wrote:
> > On Saturday 17-August-2013 10:55:07 Brian Norris wrote:
> >> On Fri, Aug 16, 2013 at 10:10:07AM +0800, Huang Shijie wrote:
> >> > We may do some ONFI get/set features operations before we call the
> >> > nand_scan_tail().
>[...]
> >  Apologies for not sending a “good copy”
> >  of the earlier one.  Sorry!
> 
> No problem. Artem had replied about resending it inline (that is the
> typical way to review patches), but I was going to get around to
> applying it anyway.

 Yes, I saw Artem's reply, and I also know Patches are
 normally sent inline.  However, to do that without it
 being corrupted (and other silly problems) from $work
 is tedious and error-prone (I omit the gory details),
 plus I wasn't available (holidays, &tc).  In any case
 the improvement is now progressing, despite the route
 to get to this point being rather strange!

cheers,
	-blf-

-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated               |  http://www.maximintegrated.com/

  reply	other threads:[~2013-08-20  7:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  2:10 [PATCH v4 0/6] Export the ECC step size to user applications Huang Shijie
2013-08-16  2:10 ` [PATCH v4 1/6] mtd: add a new field to mtd_info{} Huang Shijie
2013-08-16  2:10 ` [PATCH v4 2/6] mtd: add a new sys node to show the ecc step size Huang Shijie
2013-08-16  2:10 ` [PATCH v4 3/6] mtd: set the ecc step size for master/slave mtd_info Huang Shijie
2013-08-16  2:10 ` [PATCH v4 4/6] mtd: set ONFI nand's default hooks in nand_set_defaults() Huang Shijie
2013-08-17 17:55   ` Brian Norris
2013-08-19  8:06     ` Brian Foster
2013-08-20  0:41       ` Brian Norris
2013-08-20  7:09         ` Brian Foster [this message]
2013-08-16  2:10 ` [PATCH v4 5/6] mtd: gpmi: remove the nand_scan() Huang Shijie
2013-08-16  2:10 ` [PATCH v4 6/6] mtd: update the ABI document about the ecc step size Huang Shijie
2013-08-16 13:45   ` Artem Bityutskiy
2013-08-17  3:26     ` Huang Shijie
2013-08-17 18:14       ` Brian Norris
2013-08-18 14:29         ` Huang Shijie
2013-08-20  1:02           ` Brian Norris
2013-08-20  2:11             ` Huang Shijie
2013-08-17 18:35 ` [PATCH v4 0/6] Export the ECC step size to user applications Brian Norris
2013-08-18 14:48   ` Huang Shijie

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=2807293.aRGNn81TaS@laclwks004 \
    --to=brian.foster@maximintegrated.com \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.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