From: <Tudor.Ambarus@microchip.com>
To: <michael@walle.cc>, <p.yadav@ti.com>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>,
<Takahiro.Kuwano@infineon.com>, <tkuw584924@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/6] mtd: spi-nor: generic flash driver
Date: Tue, 26 Jul 2022 08:06:05 +0000 [thread overview]
Message-ID: <b3d5ecf7-39e4-d6f1-93a8-9efc8e352c9d@microchip.com> (raw)
In-Reply-To: <20220513133520.3945820-1-michael@walle.cc>
Hi, Takahiro,
Would you please review this patch set?
Thanks,
ta
On 5/13/22 16:35, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Add a generic flash driver, which is used when we don't find a matching
> flash in our database. All the basic features of a flash can be discovered
> by SFDP and most (if not all) newer flashes support it.
>
> Michael Walle (6):
> mtd: spi-nor: hide jedec_id sysfs attribute if not present
> mtd: spi-nor: sysfs: hide manufacturer if it is not set
> mtd: spi-nor: remember full JEDEC flash ID
> mtd: spi-nor: move function declaration out of sfdp.h
> mtd: spi-nor: add generic flash driver
> mtd: spi-nor: sysfs: print JEDEC ID for generic flash driver
>
> .../ABI/testing/sysfs-bus-spi-devices-spi-nor | 6 +++++
> drivers/mtd/spi-nor/core.c | 18 +++++++++++++
> drivers/mtd/spi-nor/core.h | 3 +++
> drivers/mtd/spi-nor/debugfs.c | 2 +-
> drivers/mtd/spi-nor/sfdp.c | 27 +++++++++++++++++++
> drivers/mtd/spi-nor/sfdp.h | 2 --
> drivers/mtd/spi-nor/sysfs.c | 20 +++++++++++++-
> include/linux/mtd/spi-nor.h | 3 +++
> 8 files changed, 77 insertions(+), 4 deletions(-)
>
> --
> 2.30.2
>
--
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-26 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 13:35 [PATCH 0/6] mtd: spi-nor: generic flash driver Michael Walle
2022-05-13 13:35 ` [PATCH 1/6] mtd: spi-nor: hide jedec_id sysfs attribute if not present Michael Walle
2022-07-26 10:00 ` Takahiro Kuwano
2022-05-13 13:35 ` [PATCH 2/6] mtd: spi-nor: sysfs: hide manufacturer if it is not set Michael Walle
2022-07-26 10:04 ` Takahiro Kuwano
2022-05-13 13:35 ` [PATCH 3/6] mtd: spi-nor: remember full JEDEC flash ID Michael Walle
2022-07-29 1:00 ` Takahiro Kuwano
2022-05-13 13:35 ` [PATCH 4/6] mtd: spi-nor: move function declaration out of sfdp.h Michael Walle
2022-07-26 23:41 ` Takahiro Kuwano
2022-05-13 13:35 ` [PATCH 5/6] mtd: spi-nor: add generic flash driver Michael Walle
2022-05-13 14:47 ` kernel test robot
2022-07-21 9:32 ` Biju Das
2022-07-21 9:48 ` Michael Walle
2022-07-21 9:52 ` Biju Das
2022-10-28 18:00 ` Biju Das
2022-07-28 3:28 ` Tudor.Ambarus
2022-07-29 1:40 ` Takahiro Kuwano
2022-05-13 13:35 ` [PATCH 6/6] mtd: spi-nor: sysfs: print JEDEC ID for " Michael Walle
2022-07-29 1:25 ` Takahiro Kuwano
2022-07-26 8:06 ` Tudor.Ambarus [this message]
2022-07-29 1:52 ` [PATCH 0/6] mtd: spi-nor: " Takahiro Kuwano
2022-07-29 5:34 ` 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=b3d5ecf7-39e4-d6f1-93a8-9efc8e352c9d@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tkuw584924@gmail.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