Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Huang Shijie <b32955@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH 1/2] mtd: nand: force NAND_CMD_READID onto 8-bit bus
Date: Fri, 31 Jan 2014 10:04:46 -0800	[thread overview]
Message-ID: <20140131180446.GA10094@norris-Latitude-E6410> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA6C9BF@DBDE04.ent.ti.com>

+ Huang

On Fri, Jan 31, 2014 at 06:55:49AM +0000, Pekon Gupta wrote:
> Though its redundant, as Ezequiel has already tested these
> patches on AM335x using both x8 and x16 Micron devices.
> But still I re-tested them on different OMAP boards.

Still worthwhile.

> Tested-By: Pekon Gupta <pekon@ti.com>

Thanks! Pushed both to l2-mtd.git/next.

BTW, I think Huang's JEDEC parameter page support should be modified
similar to patch 1. I'll comment there.

Brian

  reply	other threads:[~2014-01-31 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 22:18 [PATCH 1/2] mtd: nand: force NAND_CMD_READID onto 8-bit bus Brian Norris
2014-01-29 22:18 ` [PATCH 2/2] mtd: nand: don't use read_buf for 8-bit ONFI transfers Brian Norris
2014-01-30 12:20   ` Ezequiel Garcia
2014-01-30 12:17 ` [PATCH 1/2] mtd: nand: force NAND_CMD_READID onto 8-bit bus Ezequiel Garcia
2014-01-30 18:00   ` Brian Norris
2014-01-30 19:17 ` Gupta, Pekon
2014-01-30 19:51   ` Ezequiel Garcia
2014-01-30 20:18     ` Gupta, Pekon
2014-01-30 20:47       ` Brian Norris
2014-01-31  6:55         ` Gupta, Pekon
2014-01-31 18:04           ` Brian Norris [this message]
2014-01-30 20:39     ` Brian Norris

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=20140131180446.GA10094@norris-Latitude-E6410 \
    --to=computersforpeace@gmail.com \
    --cc=b32955@freescale.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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