From: <Tudor.Ambarus@microchip.com>
To: ludovic.Barre@st.com, marek.vasut@gmail.com
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
bbrezillon@kernel.org, richard@nod.at, alexandre.torgue@st.com,
robh+dt@kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] mtd: spi-nor: stm32: remove the driver as it was replaced by spi-stm32-qspi.c
Date: Fri, 7 Jun 2019 04:54:19 +0000 [thread overview]
Message-ID: <2940804e-2df7-066c-c9da-2e842ec74a04@microchip.com> (raw)
In-Reply-To: <1557220598-18531-1-git-send-email-ludovic.Barre@st.com>
On 05/07/2019 12:16 PM, Ludovic Barre wrote:
> From: Ludovic Barre <ludovic.barre@st.com>
>
> There's a new driver using the SPI memory interface of the
> SPI framework at spi/spi-stm32-qspi.c, which can be used
> together with m25p80.c to replace the functionality of
> this SPI NOR driver.
>
> The "new" driver uses the same dt properties and not affects
> the legacy compatibility.
>
> Signed-off-by: Ludovic Barre <ludovic.barre@st.com>
> ---
> .../devicetree/bindings/mtd/stm32-quadspi.txt | 43 --
> drivers/mtd/spi-nor/Kconfig | 7 -
> drivers/mtd/spi-nor/Makefile | 1 -
> drivers/mtd/spi-nor/stm32-quadspi.c | 720 ---------------------
> 4 files changed, 771 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mtd/stm32-quadspi.txt
> delete mode 100644 drivers/mtd/spi-nor/stm32-quadspi.c
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git,
spi-nor/next branch.
Thanks,
ta
prev parent reply other threads:[~2019-06-07 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 9:16 [PATCH] mtd: spi-nor: stm32: remove the driver as it was replaced by spi-stm32-qspi.c Ludovic Barre
2019-06-07 4:54 ` Tudor.Ambarus [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=2940804e-2df7-066c-c9da-2e842ec74a04@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=alexandre.torgue@st.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=ludovic.Barre@st.com \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).