devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Joern Engel <joern@lazybastard.org>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Sagi Grimberg <sagi@grimberg.me>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 1/6] dt-bindings: nvme: Document nvme-card compatible
Date: Tue, 6 Aug 2024 15:00:03 +0200	[thread overview]
Message-ID: <20240806130003.GA11766@lst.de> (raw)
In-Reply-To: <66b21d35.050a0220.3799b3.7e8c@mx.google.com>

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?


  reply	other threads:[~2024-08-06 13:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 11:41 [PATCH v3 0/6] mtd: improve block2mtd + airoha parser Christian Marangi
2024-08-06 11:41 ` [PATCH v3 1/6] dt-bindings: nvme: Document nvme-card compatible Christian Marangi
2024-08-06 12:42   ` Christoph Hellwig
2024-08-06 12:55     ` Christian Marangi
2024-08-06 13:00       ` Christoph Hellwig [this message]
2024-08-06 13:17         ` Christian Marangi
2024-08-06 11:41 ` [PATCH v3 2/6] nvme: assign of_node to nvme device Christian Marangi
2024-08-06 12:43   ` Christoph Hellwig
2024-08-06 13:03     ` Christian Marangi
2024-08-06 13:09       ` Christoph Hellwig
2024-08-06 13:26         ` Christian Marangi
2024-08-06 15:39       ` Dragan Simic
2024-08-06 11:41 ` [PATCH v3 3/6] dt-bindings: mmc: add property for partitions node in mmc-card node Christian Marangi
2024-08-06 11:41 ` [PATCH v3 4/6] block2mtd: attach device OF node to MTD device Christian Marangi
2024-08-06 11:41 ` [PATCH v3 5/6] dt-bindings: mtd: Add Documentation for Airoha fixed-partitions Christian Marangi
2024-08-06 11:41 ` [PATCH v3 6/6] mtd: parser: add support for Airoha parser Christian Marangi
2024-08-07 21:27   ` kernel test robot

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=20240806130003.GA11766@lst.de \
    --to=hch@lst.de \
    --cc=ansuelsmth@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=joern@lazybastard.org \
    --cc=kbusch@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=sagi@grimberg.me \
    --cc=tsbogend@alpha.franken.de \
    --cc=ulf.hansson@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).