From: Artem Bityutskiy <dedekind1@gmail.com>
To: Lei Wen <adrian.wenl@gmail.com>
Cc: Eric Miao <eric.y.miao@gmail.com>, Lei Wen <leiwen@marvell.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 1/6] pxa3xx_nand: make scan procedure more clear
Date: Mon, 07 Mar 2011 12:21:12 +0200 [thread overview]
Message-ID: <1299493272.2746.26.camel@localhost> (raw)
In-Reply-To: <AANLkTik2px-jmz0CSq03dYWjQWp2pMpdSmkKYwNWHjt=@mail.gmail.com>
On Mon, 2011-03-07 at 18:00 +0800, Lei Wen wrote:
> Hi Artem,
>
> On Mon, Mar 7, 2011 at 5:49 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Thu, 2011-03-03 at 11:08 +0800, Lei Wen wrote:
> >> The previous probe function is some kind of big part.
> >> This patch seperate the resource allocation to keep the probe process
> >> more clear than before.
> >>
> >> Signed-off-by: Lei Wen <leiwen@marvell.com>
> >> Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>
> >
> > It is a bit confusing that you sent 2 patches 1 and 6. What is in the
> > middle? Is it save to apply these 2 only?
> >
>
> I just update the patch 1 and 6, since it add the comment as you mentioned.
Ah, I see, pushed the series to my l2-mtd-2.6.git, thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-03-07 10:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:57 [PATCH V4 0/6] pxa3xx_nand update series set version 4 Lei Wen
2011-02-18 8:57 ` [PATCH 1/6] pxa3xx_nand: make scan procedure more clear Lei Wen
2011-02-18 8:57 ` [PATCH 2/6] pxa3xx_nand: rework irq logic Lei Wen
2011-02-18 8:57 ` [PATCH 3/6] pxa3xx_nand: discard wait_for_event, write_cmd, __readid function Lei Wen
2011-02-18 8:57 ` [PATCH 4/6] pxa3xx_nand: unify prepare command Lei Wen
2011-02-18 8:57 ` [PATCH 5/6] pxa3xx_nand: mtd scan id process could be defined by driver itself Lei Wen
2011-02-18 8:57 ` [PATCH 6/6] pxa3xx_nand: clean the keep configure code Lei Wen
2011-02-25 10:39 ` [PATCH V4 0/6] pxa3xx_nand update series set version 4 Artem Bityutskiy
2011-02-28 2:25 ` Lei Wen
2011-02-28 2:32 ` [PATCH 0/6] pxa3xx_nand update series set version 5 Lei Wen
2011-02-28 2:32 ` [PATCH V5 1/6] pxa3xx_nand: make scan procedure more clear Lei Wen
2011-02-28 13:55 ` Artem Bityutskiy
2011-03-03 3:00 ` Lei Wen
2011-03-03 3:08 ` Lei Wen
2011-03-07 9:49 ` Artem Bityutskiy
2011-03-07 10:00 ` Lei Wen
2011-03-07 10:21 ` Artem Bityutskiy [this message]
2011-02-28 2:32 ` [PATCH V5 2/6] pxa3xx_nand: rework irq logic Lei Wen
2011-02-28 2:32 ` [PATCH V5 3/6] pxa3xx_nand: discard wait_for_event, write_cmd, __readid function Lei Wen
2011-02-28 2:32 ` [PATCH V5 4/6] pxa3xx_nand: unify prepare command Lei Wen
2011-02-28 2:32 ` [PATCH V5 5/6] pxa3xx_nand: mtd scan id process could be defined by driver itself Lei Wen
2011-02-28 2:32 ` [PATCH V5 6/6] pxa3xx_nand: clean the keep configure code Lei Wen
2011-02-28 13:57 ` Artem Bityutskiy
2011-03-03 3:27 ` Lei Wen
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=1299493272.2746.26.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.wenl@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=haojian.zhuang@marvell.com \
--cc=leiwen@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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