From: Jianxin Pan <jianxin.pan@amlogic.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Hanjie Lin <hanjie.lin@amlogic.com>,
Victor Wan <victor.wan@amlogic.com>,
Marek Vasut <marek.vasut@gmail.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Richard Weinberger <richard@nod.at>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
Boris Brezillon <boris.brezillon@bootlin.com>,
Jian Hu <jian.hu@amlogic.com>,
Liang Yang <liang.yang@amlogic.com>,
linux-mtd@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>,
Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v8 0/2] mtd: rawnand: meson: add Amlogic NAND driver support
Date: Tue, 15 Jan 2019 23:44:08 +0800 [thread overview]
Message-ID: <18ad7184-3bbe-4bd1-826a-fce5d31c215c@amlogic.com> (raw)
In-Reply-To: <20190115094911.75f4edc9@xps13>
Hi Miquel,
On 2019/1/15 16:49, Miquel Raynal wrote:
> Hi Jianxin,
>
> Jianxin Pan <jianxin.pan@amlogic.com> wrote on Sun, 16 Dec 2018
> 23:17:41 +0800:
>
>> These two patches try to add initial NAND driver support for Amlogic Meson
>> SoCs, current it has been tested on GXL(p212) and AXG(s400) platform.
>>
>> Changes since V6 at [8]
>> - fix bitflips checking for blank pages
>> - trace the latest commit with nand/next branch
>> - checking the return of meson_nand_op_get_dma_safe_*input/output*_buf
>> - add .detach_chip for free meson_nand.data_buf/info_buf
>>
>
> Can you send a v9 with the build failre (object_is_on_stack pb) fixed
> and the Kconfig entry updated (the Meson common clock thing) as
> suggested by Martin?
I sent v9 just now, object_is_on_stack build fail is fixed and Kconfig is updated as Martin suggested.
Thank you for your time.
>
>
> Thanks,
> Miquèl
>
> .
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-01-15 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 15:17 [PATCH v8 0/2] mtd: rawnand: meson: add Amlogic NAND driver support Jianxin Pan
2018-12-16 15:17 ` [PATCH v8 1/2] dt-bindings: nand: meson: add Amlogic NAND controller driver Jianxin Pan
2018-12-16 15:17 ` [PATCH v8 2/2] mtd: rawnand: meson: add support for Amlogic NAND flash controller Jianxin Pan
2018-12-18 15:57 ` kbuild test robot
2019-01-15 8:49 ` [PATCH v8 0/2] mtd: rawnand: meson: add Amlogic NAND driver support Miquel Raynal
2019-01-15 15:44 ` Jianxin Pan [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=18ad7184-3bbe-4bd1-826a-fce5d31c215c@amlogic.com \
--to=jianxin.pan@amlogic.com \
--cc=boris.brezillon@bootlin.com \
--cc=carlo@caione.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=hanjie.lin@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=jian.hu@amlogic.com \
--cc=khilman@baylibre.com \
--cc=liang.yang@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=narmstrong@baylibre.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=victor.wan@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;
as well as URLs for NNTP newsgroup(s).