From: Artem Bityutskiy <dedekind1@gmail.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Matthieu CASTET <matthieu.castet@parrot.com>,
Brian Norris <norris@broadcom.com>,
Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH 0/4 v2] NAND: add support for reading ONFI parameters
Date: Mon, 30 Aug 2010 11:36:16 +0300 [thread overview]
Message-ID: <1283157376.12995.24.camel@brekeke> (raw)
In-Reply-To: <1283156633.12995.21.camel@brekeke>
On Mon, 2010-08-30 at 11:23 +0300, Artem Bityutskiy wrote:
> On Wed, 2010-08-18 at 14:01 +0200, Florian Fainelli wrote:
> > Hi,
> >
> > This is the second version of the patch series adding support for ONFI
> > parameters to NAND device.
> >
> > Florian Fainelli (4):
> > NAND: add NAND_CMD_PARAM (0xec) definition
> > NAND: denali should also handle NAND_CMD_PARAM
> > lib: add crc16_le helper
> > NAND: add support for reading ONFI parameters from NAND device
>
> Hi,
>
> since I did not review your patches, I am picking them and pushing to
> l2-mtd-2.6.git / dunno branch. I'll try to encourage dwmw2 to look at
> them and take them to the mtd tree, so they would have some exposure in
> the -next tree.
>
> But some "Tested-by" / "Reviewed-by" tags would certainly be useful,
> anyone?
OK, I've noticed the further discussion. Your patches are not threaded
with this e-mail, and this confused me.
So I'm removing your patches from my tree and waiting for newer
patch-set.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-08-30 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 12:01 [PATCH 0/4 v2] NAND: add support for reading ONFI parameters Florian Fainelli
2010-08-30 8:23 ` Artem Bityutskiy
2010-08-30 8:36 ` Artem Bityutskiy [this message]
2010-08-30 8:52 ` Florian Fainelli
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=1283157376.12995.24.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=florian@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=mbizon@freebox.fr \
--cc=norris@broadcom.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).