From: John Garry <john.garry@huawei.com>
To: <corbet@lwn.net>, <mchehab+samsung@kernel.org>,
<linux-mtd@lists.infradead.org>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<frieder.schrempf@kontron.de>, John Garry <john.garry@huawei.com>
Subject: [PATCH] docs: mtd: Update spi nor reference driver
Date: Wed, 7 Aug 2019 00:06:23 +0800 [thread overview]
Message-ID: <1565107583-68506-1-git-send-email-john.garry@huawei.com> (raw)
The reference driver no longer exists since commit 50f1242c6742 ("mtd:
fsl-quadspi: Remove the driver as it was replaced by spi-fsl-qspi.c").
Update reference to spi-fsl-qspi.c driver.
Signed-off-by: John Garry <john.garry@huawei.com>
diff --git a/Documentation/driver-api/mtd/spi-nor.rst b/Documentation/driver-api/mtd/spi-nor.rst
index f5333e3bf486..1f0437676762 100644
--- a/Documentation/driver-api/mtd/spi-nor.rst
+++ b/Documentation/driver-api/mtd/spi-nor.rst
@@ -59,7 +59,7 @@ Part III - How can drivers use the framework?
The main API is spi_nor_scan(). Before you call the hook, a driver should
initialize the necessary fields for spi_nor{}. Please see
-drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to fsl-quadspi.c
+drivers/mtd/spi-nor/spi-nor.c for detail. Please also refer to spi-fsl-qspi.c
when you want to write a new driver for a SPI NOR controller.
Another API is spi_nor_restore(), this is used to restore the status of SPI
flash chip such as addressing mode. Call it whenever detach the driver from
--
2.17.1
next reply other threads:[~2019-08-06 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 16:06 John Garry [this message]
2019-08-06 16:35 ` [PATCH] docs: mtd: Update spi nor reference driver John Garry
2019-08-06 16:40 ` Schrempf Frieder
2019-08-16 10:20 ` John Garry
2019-08-19 4:39 ` Vignesh Raghavendra
2019-08-20 14:09 ` John Garry
2019-08-20 16:58 ` Mark Brown
2019-08-21 13:39 ` John Garry
2019-09-06 14:52 ` Jonathan Corbet
2019-09-06 14:58 ` John Garry
2019-09-06 15:03 ` Jonathan Corbet
2019-09-06 15:10 ` Tudor.Ambarus
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=1565107583-68506-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=corbet@lwn.net \
--cc=frieder.schrempf@kontron.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mchehab+samsung@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).