[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3bb5ae427dc01b82be4434dff39e6c8e@walle.cc>
Date: Thu, 17 Jun 2021 16:19:34 +0200
From: Michael Walle <michael@...le.cc>
To: Reto Schneider <code@...o-schneider.ch>
Cc: linux-mtd@...ts.infradead.org, Stefan Roese <sr@...x.de>,
Reto Schneider <reto.schneider@...qvarnagroup.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Pratyush Yadav <p.yadav@...com>,
Richard Weinberger <richard@....at>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Vignesh Raghavendra <vigneshr@...com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] mtd: spi-nor: Add support for XM25QH64C
Hi Reto,
Am 2021-06-17 13:59, schrieb Reto Schneider:
>> NB. XMC ignores the continuation codes and this particular device will
>> collide with M25PE64/M45PE64. Although I couldn't find any datasheet,
>> so I don't know if these devices actually exist.
>
> M25PE64 yields quite some hits on Google. Is supporting this (all?)
> XMC device in upstream a good idea nevertheless? Does "first come,
> first served" apply here?
That is up to the maintainers, but sooner or later we will have to face
the problem regarding the duplicate IDs.
-michael
Powered by blists - more mailing lists