From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: liang.yang@amlogic.com, linux-amlogic@lists.infradead.org,
linux-mtd@lists.infradead.org, richard@nod.at,
linux-arm-kernel@lists.infradead.org, marek.vasut@gmail.com,
linux-kernel@vger.kernel.org, computersforpeace@gmail.com,
dwmw2@infradead.org, bbrezillon@kernel.org,
jianxin.pan@amlogic.com
Subject: Re: [PATCH 0/4] meson-nand: small code improvements
Date: Thu, 18 Apr 2019 18:22:59 +0200 [thread overview]
Message-ID: <20190418182259.479bbeb3@xps13> (raw)
In-Reply-To: <20190411220056.19109-1-martin.blumenstingl@googlemail.com>
Hi Martin,
Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote on Fri,
12 Apr 2019 00:00:52 +0200:
> This series comes with four small improvements for the meson-nand
> driver:
> * the first patches are replacing open-coded logic with existing
> utilities / helpers
> * the third patch drops some unnecessary casting after changing
> the type of the info buffer parameter from "u8 *" to "void *"
> * the fourth patch adjusts the usage of init_completion with what the
> documentation suggests
>
> I have tested these patches as best as I could on my Meson8m2 board
> using experimental patches on top of this series which add support for
> this older SoC to the meson-nand driver.
>
> Liang, can you please test this series on GXL and/or AXG so I don't
> break the NFC driver on these newer SoCs? All of my GXL/GXM boards
> have eMMC instead of raw NAND, so I cannot test it on these newer SoCs
> myself.
>
> This series is meant to be applied to the nand/next tree.
>
>
> Martin Blumenstingl (4):
> mtd: rawnand: meson: use struct_size macro
> mtd: rawnand: meson: use of_property_count_elems_of_size helper
> mtd: rawnand: meson: use a void pointer for meson_nfc_dma_buffer_setup
> mtd: rawnand: meson: only initialize the RB completion once
>
> drivers/mtd/nand/raw/meson_nand.c | 21 +++++++++------------
> 1 file changed, 9 insertions(+), 12 deletions(-)
>
Series applied to
https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
branch nand/next.
Thanks,
Miquèl
prev parent reply other threads:[~2019-04-18 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 22:00 [PATCH 0/4] meson-nand: small code improvements Martin Blumenstingl
2019-04-11 22:00 ` [PATCH 1/4] mtd: rawnand: meson: use struct_size macro Martin Blumenstingl
2019-04-15 6:01 ` Liang Yang
2019-04-11 22:00 ` [PATCH 2/4] mtd: rawnand: meson: use of_property_count_elems_of_size helper Martin Blumenstingl
2019-04-15 6:02 ` Liang Yang
2019-04-11 22:00 ` [PATCH 3/4] mtd: rawnand: meson: use a void pointer for meson_nfc_dma_buffer_setup Martin Blumenstingl
2019-04-15 6:03 ` Liang Yang
2019-04-11 22:00 ` [PATCH 4/4] mtd: rawnand: meson: only initialize the RB completion once Martin Blumenstingl
2019-04-15 6:04 ` Liang Yang
2019-04-18 19:44 ` Martin Blumenstingl
2019-04-19 3:52 ` Liang Yang
2019-04-19 9:00 ` Miquel Raynal
2019-04-18 16:22 ` Miquel Raynal [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=20190418182259.479bbeb3@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jianxin.pan@amlogic.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=richard@nod.at \
/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).