linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	linux-mtd@lists.infradead.org,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Richard Weinberger <richard@nod.at>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: spi-nor: Convert to DT schema format
Date: Tue, 9 Feb 2021 15:23:17 -0600	[thread overview]
Message-ID: <20210209212317.GA214117@robh.at.kernel.org> (raw)
In-Reply-To: <20210202175340.3902494-1-robh@kernel.org>

On Tue, 02 Feb 2021 11:53:39 -0600, Rob Herring wrote:
> Convert the SPI-NOR binding to DT schema format. Like other memory chips,
> the compatible strings are a mess with vendor prefixes not being used
> consistently and some compatibles not documented. The resulting schema
> passes on 'compatible' checks for most in tree users with the exception
> of some oddballs.
> 
> I dropped the 'm25p.*-nonjedec' compatible strings as these don't appear
> to be used anywhere.
> 
> Cc: Miquel Raynal <miquel.raynal@bootlin.com>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Vignesh Raghavendra <vigneshr@ti.com>
> Cc: linux-mtd@lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  .../devicetree/bindings/mtd/jedec,spi-nor.txt |  91 ----------------
>  .../bindings/mtd/jedec,spi-nor.yaml           | 102 ++++++++++++++++++
>  2 files changed, 102 insertions(+), 91 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/mtd/jedec,spi-nor.txt
>  create mode 100644 Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
> 

Applied, thanks!

  reply	other threads:[~2021-02-10  1:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 17:53 [PATCH] dt-bindings: mtd: spi-nor: Convert to DT schema format Rob Herring
2021-02-09 21:23 ` Rob Herring [this message]
2021-02-16  9:12 ` Geert Uytterhoeven

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=20210209212317.GA214117@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --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;
as well as URLs for NNTP newsgroup(s).