From: Michael Walle <michael@walle.cc>
To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Richard Weinberger <richard@nod.at>,
Michael Walle <michael@walle.cc>,
Boris Brezillon <boris.brezillon@collabora.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH v4 0/3] mtd: spi-nor: keep lock bits if they are non-volatile
Date: Sat, 3 Oct 2020 16:17:35 +0200 [thread overview]
Message-ID: <20201003141738.8144-1-michael@walle.cc> (raw)
I bundled this as a series, because otherwise there will be conflicts
because the "remove global protection flag" patches modify the same lines
as the main patch.
See invdividual patches for the version history.
Michael Walle (3):
mtd: spi-nor: atmel: remove global protection flag
mtd: spi-nor: sst: remove global protection flag
mtd: spi-nor: keep lock bits if they are non-volatile
drivers/mtd/spi-nor/Kconfig | 42 ++++++++++++
drivers/mtd/spi-nor/atmel.c | 129 ++++++++++++++++++++++++++++++------
drivers/mtd/spi-nor/core.c | 36 +++++++---
drivers/mtd/spi-nor/core.h | 8 +++
drivers/mtd/spi-nor/esmt.c | 8 ++-
drivers/mtd/spi-nor/intel.c | 6 +-
drivers/mtd/spi-nor/sst.c | 31 ++++-----
7 files changed, 206 insertions(+), 54 deletions(-)
--
2.20.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-10-03 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 14:17 Michael Walle [this message]
2020-10-03 14:17 ` [PATCH v4 1/3] mtd: spi-nor: atmel: remove global protection flag Michael Walle
2020-10-03 14:17 ` [PATCH v4 2/3] mtd: spi-nor: sst: " Michael Walle
2020-10-03 14:17 ` [PATCH v4 3/3] mtd: spi-nor: keep lock bits if they are non-volatile Michael Walle
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=20201003141738.8144-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=boris.brezillon@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--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).