public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
	Pratyush Yadav <p.yadav@ti.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	yaliang.wang@windriver.com, Michael Walle <michael@walle.cc>
Subject: [PATCH v4 08/32] mtd: spi-nor: intel: unify function names
Date: Mon, 21 Feb 2022 13:07:45 +0100	[thread overview]
Message-ID: <20220221120809.1531502-9-michael@walle.cc> (raw)
In-Reply-To: <20220221120809.1531502-1-michael@walle.cc>

To avoid name clashes unify all the function and static object names and
use one of the following prefixes which should be sufficiently unique:
 - <vendor>_nor_
 - <flash_family>_nor_
 - <flash_part>_

There are no functional changes.

Signed-off-by: Michael Walle <michael@walle.cc>
---
 drivers/mtd/spi-nor/intel.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/mtd/spi-nor/intel.c b/drivers/mtd/spi-nor/intel.c
index d64e114e9fb4..9179f2d09cba 100644
--- a/drivers/mtd/spi-nor/intel.c
+++ b/drivers/mtd/spi-nor/intel.c
@@ -8,7 +8,7 @@
 
 #include "core.h"
 
-static const struct flash_info intel_parts[] = {
+static const struct flash_info intel_nor_parts[] = {
 	/* Intel/Numonyx -- xxxs33b */
 	{ "160s33b",  INFO(0x898911, 0, 64 * 1024,  32)
 		FLAGS(SPI_NOR_HAS_LOCK | SPI_NOR_SWP_IS_VOLATILE) },
@@ -20,6 +20,6 @@ static const struct flash_info intel_parts[] = {
 
 const struct spi_nor_manufacturer spi_nor_intel = {
 	.name = "intel",
-	.parts = intel_parts,
-	.nparts = ARRAY_SIZE(intel_parts),
+	.parts = intel_nor_parts,
+	.nparts = ARRAY_SIZE(intel_nor_parts),
 };
-- 
2.30.2


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2022-02-21 12:11 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 12:07 [PATCH v4 00/32] mtd: spi-nor: move vendor specific code into vendor modules Michael Walle
2022-02-21 12:07 ` [PATCH v4 01/32] mtd: spi-nor: atmel: unify function names Michael Walle
2022-02-22  7:23   ` Pratyush Yadav
2022-02-22  7:26     ` Michael Walle
2022-02-23 11:33       ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 02/32] mtd: spi-nor: catalyst: " Michael Walle
2022-02-23 11:33   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 03/32] mtd: spi-nor: eon: " Michael Walle
2022-02-23 11:33   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 04/32] mtd: spi-nor: esmt: " Michael Walle
2022-02-23 11:34   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 05/32] mtd: spi-nor: everspin: " Michael Walle
2022-02-23 11:34   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 06/32] mtd: spi-nor: fujitsu: " Michael Walle
2022-02-23 11:35   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 07/32] mtd: spi-nor: gigadevice: " Michael Walle
2022-02-23 11:35   ` Pratyush Yadav
2022-02-21 12:07 ` Michael Walle [this message]
2022-02-23 11:35   ` [PATCH v4 08/32] mtd: spi-nor: intel: " Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 09/32] mtd: spi-nor: issi: " Michael Walle
2022-02-23 11:36   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 10/32] mtd: spi-nor: macronix: " Michael Walle
2022-02-23 11:36   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 11/32] mtd: spi-nor: micron-st: " Michael Walle
2022-02-23 11:37   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 12/32] mtd: spi-nor: spansion: " Michael Walle
2022-02-23 11:37   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 13/32] mtd: spi-nor: sst: " Michael Walle
2022-02-23 11:38   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 14/32] mtd: spi-nor: winbond: " Michael Walle
2022-02-23 11:38   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 15/32] mtd: spi-nor: xilinx: " Michael Walle
2022-02-23 11:39   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 16/32] mtd: spi-nor: xmc: " Michael Walle
2022-02-23 11:40   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 17/32] mtd: spi-nor: slightly refactor the spi_nor_setup() Michael Walle
2022-02-21 12:07 ` [PATCH v4 18/32] mtd: spi-nor: allow a flash to define its own ready() function Michael Walle
2022-02-21 12:07 ` [PATCH v4 19/32] mtd: spi-nor: export more function to be used in vendor modules Michael Walle
2022-02-21 12:07 ` [PATCH v4 20/32] mtd: spi-nor: guard _page_size parameter in S3AN_INFO() Michael Walle
2022-02-22  7:26   ` Pratyush Yadav
2022-02-21 12:07 ` [PATCH v4 21/32] mtd: spi-nor: move all xilinx specifics into xilinx.c Michael Walle
2022-02-21 12:07 ` [PATCH v4 22/32] mtd: spi-nor: xilinx: rename vendor specific functions and defines Michael Walle
2022-02-23 11:51   ` Pratyush Yadav
2022-02-21 12:08 ` [PATCH v4 23/32] mtd: spi-nor: xilinx: correct the debug message Michael Walle
2022-02-21 12:08 ` [PATCH v4 24/32] mtd: spi-nor: move all micron-st specifics into micron-st.c Michael Walle
2022-02-21 12:08 ` [PATCH v4 25/32] mtd: spi-nor: micron-st: convert USE_FSR to a manufacturer flag Michael Walle
2022-02-21 12:08 ` [PATCH v4 26/32] mtd: spi-nor: micron-st: rename vendor specific functions and defines Michael Walle
2022-02-23 11:54   ` Pratyush Yadav
2022-02-21 12:08 ` [PATCH v4 27/32] mtd: spi-nor: spansion: slightly rework control flow in late_init() Michael Walle
2022-02-21 12:08 ` [PATCH v4 28/32] mtd: spi-nor: move all spansion specifics into spansion.c Michael Walle
2022-02-23 11:59   ` Pratyush Yadav
2022-02-21 12:08 ` [PATCH v4 29/32] mtd: spi-nor: spansion: convert USE_CLSR to a manufacturer flag Michael Walle
2022-02-21 12:08 ` [PATCH v4 30/32] mtd: spi-nor: spansion: rename vendor specific functions and defines Michael Walle
2022-02-23 12:01   ` Pratyush Yadav
2022-02-21 12:08 ` [PATCH v4 31/32] mtd: spi-nor: slightly change code style in spi_nor_sr_ready() Michael Walle
2022-02-23 12:00   ` Pratyush Yadav
2022-02-21 12:08 ` [PATCH v4 32/32] mtd: spi-nor: renumber flags Michael Walle
2022-02-22  8:59 ` [PATCH v4 00/32] mtd: spi-nor: move vendor specific code into vendor modules Tudor.Ambarus
2022-02-23 11:30   ` Pratyush Yadav

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=20220221120809.1531502-9-michael@walle.cc \
    --to=michael@walle.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=p.yadav@ti.com \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@microchip.com \
    --cc=vigneshr@ti.com \
    --cc=yaliang.wang@windriver.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