[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161812694422.37194.1007833046830132290.b4-ty@microchip.com>
Date: Sun, 11 Apr 2021 10:45:04 +0300
From: Tudor Ambarus <tudor.ambarus@...rochip.com>
To: Tudor Ambarus <tudor.ambarus@...rochip.com>, <michael@...le.cc>,
<ycllin@...c.com.tw>, <p.yadav@...com>, <vigneshr@...com>,
<masonccyang@...c.com.tw>, <zhengxunli@...c.com.tw>,
<juliensu@...c.com.tw>
CC: <linux-mtd@...ts.infradead.org>, <miquel.raynal@...tlin.com>,
<richard@....at>, <linux-kernel@...r.kernel.org>
Subject: Re: (subset)[PATCH 0/2] mtd: spi-nor: macronix: mx25l51245g, mx66l51235l and mx66l51235f
On Fri, 2 Apr 2021 11:20:29 +0300, Tudor Ambarus wrote:
> mx25l51245g and mx66l51235l have the same flash ID. The flash
> detection returns the first entry in the flash_info array that
> matches the flash ID that was read, thus for the 0xc2201a ID,
> mx25l51245g was always hit, introducing a regression for
> mx66l51235l. Revert mx25l51245g addition. A solution for these
> flashes to coexist was proposed.
>
> [...]
Applied to spi-nor/next, thanks!
[1/2] Revert "mtd: spi-nor: macronix: Add support for mx25l51245g"
https://git.kernel.org/mtd/c/46094049a49b
Best regards,
--
Tudor Ambarus <tudor.ambarus@...rochip.com>
Powered by blists - more mailing lists