From: <Tudor.Ambarus@microchip.com>
To: <broonie@kernel.org>
Cc: <gch981213@gmail.com>, <linux-mediatek@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<devicetree@vger.kernel.org>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <robh+dt@kernel.org>,
<matthias.bgg@gmail.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 07:41:26 +0000 [thread overview]
Message-ID: <2471214.x7VzW1FXlQ@localhost.localdomain> (raw)
In-Reply-To: <20200309121020.GD4101@sirena.org.uk>
Hi, Mark,
On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > This driver is superseded by the new spi-mtk-nor driver.
> >
> > Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
>
> Is this move OK from a MTD point of view - should I apply this when the
> rest goes in? The patch was in prior versions too and is obviously
> straightforward.
If you find the rest of the patches ok, this can go through the spi tree, feel
free to add my
Acked-by: Tudor Ambarus <tudor.ambarus@microchip.com>
There will be a conflict with the following patch https://
patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
I'll try to allocate time for reviewing the remaining patches in this set in
the following days.
Cheers,
ta
next prev parent reply other threads:[~2020-03-10 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 8:50 [PATCH v3 0/4] rewrite mtk-quadspi spi-nor driver with spi-mem Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 1/4] spi: make spi-max-frequency optional Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 2/4] spi: add support for mediatek spi-nor controller Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 3/4] dt-bindings: convert mtk-quadspi binding doc for spi-mtk-nor Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver Chuanhong Guo
2020-03-09 12:10 ` Mark Brown
2020-03-10 7:41 ` Tudor.Ambarus [this message]
2020-03-10 9:11 ` Tudor.Ambarus
2020-03-11 19:57 ` Mark Brown
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=2471214.x7VzW1FXlQ@localhost.localdomain \
--to=tudor.ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).