From: Michael Walle <michael@walle.cc>
To: Reto Schneider <code@reto-schneider.ch>
Cc: linux-mtd@lists.infradead.org, Stefan Roese <sr@denx.de>,
Reto Schneider <reto.schneider@husqvarnagroup.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Pratyush Yadav <p.yadav@ti.com>,
Richard Weinberger <richard@nod.at>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mtd: spi-nor: Add support for XM25QH64C
Date: Thu, 17 Jun 2021 16:19:34 +0200 [thread overview]
Message-ID: <3bb5ae427dc01b82be4434dff39e6c8e@walle.cc> (raw)
In-Reply-To: <f022abf3-a6fe-d060-9868-985303c4e8a0@reto-schneider.ch>
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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-06-17 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 12:12 [PATCH v1] mtd: spi-nor: Add support for XM25QH64C Reto Schneider
2021-06-14 6:56 ` Michael Walle
2021-06-17 11:59 ` Reto Schneider
2021-06-17 14:19 ` Michael Walle [this message]
2021-06-17 15:06 ` Reto Schneider
2021-06-28 5:17 ` Tudor.Ambarus
2021-06-28 4:55 ` Tudor.Ambarus
2021-06-30 14:15 ` Michael Walle
2021-06-30 18:28 ` Tudor.Ambarus
2021-07-01 5:25 ` Tudor.Ambarus
2021-07-01 6:15 ` Michael Walle
2021-06-28 5: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=3bb5ae427dc01b82be4434dff39e6c8e@walle.cc \
--to=michael@walle.cc \
--cc=code@reto-schneider.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=reto.schneider@husqvarnagroup.com \
--cc=richard@nod.at \
--cc=sr@denx.de \
--cc=tudor.ambarus@microchip.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