From: Rob Herring <robh@kernel.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski@canonical.com,
richard@nod.at, linux-mtd@lists.infradead.org,
linus.walleij@linaro.org, vigneshr@ti.com,
linux-arm-kernel@lists.infradead.org, miquel.raynal@bootlin.com
Subject: Re: [PATCH v3] dt-bindings: mtd: drop mtd/cortina,gemini-flash.txt
Date: Thu, 17 Feb 2022 17:37:11 -0600 [thread overview]
Message-ID: <Yg7cJzAsGo4pcb25@robh.at.kernel.org> (raw)
In-Reply-To: <20220211120842.3388592-1-clabbe@baylibre.com>
On Fri, 11 Feb 2022 12:08:42 +0000, Corentin Labbe wrote:
> Drop mtd/cortina,gemini-flash.txt since it is nearly already handled by
> Documentation/devicetree/bindings/mtd/mtd-physmap.yaml.
>
> We add jedec-flash to list of compatible because one board (gemini-dlink-dns-313.dts) needs it.
> See commit a10d862e585e ("ARM: dts: Fix the DNS-313 flash compatible")
> The flash on the DNS-313 needs to be probed as JEDEC, it does not conform to the common CFI standard.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> ---
> Change since v1
> - fixed typo in syscon
>
> Change since v2
> - Added reason of adding jedec-flash
>
> .../bindings/mtd/cortina,gemini-flash.txt | 24 -------------------
> .../devicetree/bindings/mtd/mtd-physmap.yaml | 18 +++++++++++++-
> 2 files changed, 17 insertions(+), 25 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mtd/cortina,gemini-flash.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-17 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 12:08 [PATCH v3] dt-bindings: mtd: drop mtd/cortina,gemini-flash.txt Corentin Labbe
2022-02-15 15:22 ` Rob Herring
2022-02-17 23:37 ` Rob Herring [this message]
2022-02-18 14:32 ` Miquel Raynal
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=Yg7cJzAsGo4pcb25@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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).