From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mauro Lima <mauro.lima@eclypsium.com>
Cc: linux-mtd@lists.infradead.org, daniel.gutson@eclypsium.com,
richard@hughsie.com, tudor.ambarus@microchip.com,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com
Subject: Re: [PATCH 4/4] mtd: intel-spi: add read only stubs
Date: Mon, 13 Sep 2021 13:06:00 +0300 [thread overview]
Message-ID: <YT8iiCHFvhb1AEhp@lahna> (raw)
In-Reply-To: <20210910211348.642103-5-mauro.lima@eclypsium.com>
On Fri, Sep 10, 2021 at 06:13:48PM -0300, Mauro Lima wrote:
> Add read only stub functions (as __weak) in read only mode,
> so they can be override on read-write mode.
> Remove the (DANGEROUS) tag in read only mode.
> Add write mode option if pci or platform driver is selected.
> Change the intel-spi recepie to be able to build read only
> or read-write mode.
This looks pretty convoluted way to get rid of the "DANGEROUS" in the
name ;-)
What is the firmware information fwupd is looking for? Perhaps there are
other, better, ways to do this?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-09-13 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 21:13 [PATCH 0/4] mtd: intel-spi: split read/write modes Mauro Lima
2021-09-10 21:13 ` [PATCH 1/4] mtd: intel-spi: rename intel-spi to intel-spi-base Mauro Lima
2021-09-13 10:00 ` Mika Westerberg
2021-09-10 21:13 ` [PATCH 2/4] mtd: intel-spi: move chip internals into a defs.h Mauro Lima
2021-09-10 21:13 ` [PATCH 3/4] mtd: intel-spi: moving write/erase functions Mauro Lima
2021-09-10 21:13 ` [PATCH 4/4] mtd: intel-spi: add read only stubs Mauro Lima
2021-09-13 10:06 ` Mika Westerberg [this message]
2021-09-13 9:59 ` [PATCH 0/4] mtd: intel-spi: split read/write modes Mika Westerberg
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=YT8iiCHFvhb1AEhp@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=daniel.gutson@eclypsium.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mauro.lima@eclypsium.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@hughsie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.