[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zvz6ITaMKmo0U3c3@infradead.org>
Date: Wed, 2 Oct 2024 00:45:37 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>, Jens Axboe <axboe@...nel.dk>,
Jonathan Corbet <corbet@....net>,
Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
INAGAKI Hiroshi <musashino.open@...il.com>,
Daniel Golle <daniel@...rotopia.org>,
Christian Brauner <brauner@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>, Ming Lei <ming.lei@...hat.com>,
Li Lingfeng <lilingfeng3@...wei.com>,
Christian Heusel <christian@...sel.eu>, linux-block@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
Miquel Raynal <miquel.raynal@...tlin.com>,
Lorenzo Bianconi <lorenzo@...nel.org>
Subject: Re: [RFC PATCH 3/4] block: add support for partition table defined
in OF
On Tue, Oct 01, 2024 at 11:26:22AM +0200, Christian Marangi wrote:
> > No. ->disk_name is in no way reliable, we can't hardcode that into
> > a partition parser.
> >
>
> Then any hint on this or alternative way?
The normal way would be to use eui/ngui/uuid provided by the storage
device. We have a interface for that in the block layer support by
scsi and nvme, but I don't know how to wire that up for eMMC which
I suspect is what you care about.
Powered by blists - more mailing lists