From: Fabio Estevam <festevam@denx.de>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: pratyush@kernel.org, michael@walle.cc,
linux-mtd@lists.infradead.org, takahiro.kuwano@infineon.com,
bacem.daassi@infineon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] mtd: spi-nor: introduce die erase
Date: Sat, 25 Nov 2023 14:29:20 -0300 [thread overview]
Message-ID: <6156a51f7eadc9594404bb0eacabe1a6@denx.de> (raw)
In-Reply-To: <d7ce98eb-c920-413f-bbe9-059077a9dda7@linaro.org>
Hi Tudor,
On 25/11/2023 09:37, Tudor Ambarus wrote:
> I made a typo on Fabio's email address. Now added correctly.
It looks like the Subject of patch 3/5 is not complete:
[PATCH v3 3/5] mtd: spi-nor: micron-st: "
Feel free to add to this series:
Tested-by: Fabio Estevam <festevam@denx.de>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-11-25 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:35 [PATCH v3 0/5] mtd: spi-nor: introduce die erase Tudor Ambarus
2023-11-25 12:35 ` [PATCH v3 1/5] mtd: spi-nor: add erase die (chip) capability Tudor Ambarus
2023-11-25 12:35 ` [PATCH v3 2/5] mtd: spi-nor: spansion: enable die erase for multi die flashes Tudor Ambarus
2023-11-25 12:35 ` [PATCH v3 3/5] mtd: spi-nor: micron-st: " Tudor Ambarus
2023-11-25 12:35 ` [PATCH v3 4/5] mtd: spi-nor: remove NO_CHIP_ERASE flag Tudor Ambarus
2023-11-25 12:35 ` [PATCH v3 5/5] mtd: spi-nor: micron-st: Add support for mt25qu01g Tudor Ambarus
2023-11-25 12:37 ` [PATCH v3 0/5] mtd: spi-nor: introduce die erase Tudor Ambarus
2023-11-25 17:29 ` Fabio Estevam [this message]
2023-11-30 10:42 ` Tudor Ambarus
2023-12-04 20:59 ` Fabio Estevam
2023-12-05 7:40 ` Tudor Ambarus
2023-12-06 9:32 ` 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=6156a51f7eadc9594404bb0eacabe1a6@denx.de \
--to=festevam@denx.de \
--cc=bacem.daassi@infineon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=takahiro.kuwano@infineon.com \
--cc=tudor.ambarus@linaro.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