From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: <masonccyang@mxic.com.tw>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <juliensu@mxic.com.tw>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] mtd: spi-nor: macronix: Add support for mx25l512/mx25u512
Date: Tue, 28 Apr 2020 08:39:15 +0000 [thread overview]
Message-ID: <2988068.fH3nZIc59V@192.168.0.120> (raw)
In-Reply-To: <1587631123-25474-1-git-send-email-masonccyang@mxic.com.tw>
On Thursday, April 23, 2020 11:38:41 AM EEST Mason Yang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hi,
>
> mx25l51245g/mx25u51245g is a mass production for new design and
> replace mx66l51235l/mx66u51235f(phase out).
>
> Validated by read, erase, read back, write and read back
> on Xilinx Zynq PicoZed FPGA board which included
> Macronix SPI Host (driver/spi/spi-mxic.c).
>
> change log:
> v2:
> Add which controller we tested the mx25l/u51245g.
>
> Mason Yang (2):
> mtd: spi-nor: macronix: Add support for mx25l51245g
> mtd: spi-nor: macronix: Add support for mx25u51245g
>
> drivers/mtd/spi-nor/macronix.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Both applied. In 2/2 I ordered the entry alphabetically. Would you send a
patch to order all entries in macronix.c in alphabetical order? It's a mess
right now.
Cheers,
ta
next prev parent reply other threads:[~2020-04-28 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 8:38 Mason Yang
2020-04-23 8:38 ` [PATCH v2 1/2] mtd: spi-nor: macronix: Add support for mx25l51245g Mason Yang
2020-04-23 8:38 ` [PATCH v2 2/2] mtd: spi-nor: macronix: Add support for mx25u51245g Mason Yang
2020-04-28 8:39 ` Tudor.Ambarus [this message]
2020-04-29 5:53 ` [PATCH v2 0/2] mtd: spi-nor: macronix: Add support for mx25l512/mx25u512 masonccyang
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=2988068.fH3nZIc59V@192.168.0.120 \
--to=tudor.ambarus@microchip.com \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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
all inboxes | Powered by JetHome®