[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240806130003.GA11766@lst.de>
Date: Tue, 6 Aug 2024 15:00:03 +0200
From: Christoph Hellwig <hch@....de>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Christoph Hellwig <hch@....de>, Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Joern Engel <joern@...ybastard.org>,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Sagi Grimberg <sagi@...mberg.me>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Florian Fainelli <f.fainelli@...il.com>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v3 1/6] dt-bindings: nvme: Document nvme-card compatible
I don't see how this works. There is absolutely nothing nvme specific
in there, and we really should not bring OF into NVMe.
> (alternative is to have in block2mtd all kind of extra logic with switch
> case to check for major block ID that deviates from a common schema)
What common scheme?
Powered by blists - more mailing lists