From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Guochun Mao <guochun.mao@mediatek.com>,
Richard Weinberger <richard@nod.at>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-mtd@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] arm: dts: mt2701: add nor flash node
Date: Tue, 17 Jan 2017 14:32:08 +1100 [thread overview]
Message-ID: <20170117143208.03c9af83@free-electrons.com> (raw)
In-Reply-To: <20170113175628.1793f433@bbrezillon>
Hello,
On Fri, 13 Jan 2017 17:56:28 +0100, Boris Brezillon wrote:
> because both compatible are referring to very specific IP version. It's
> not the same as
>
> compatible = "mediatek,mt8173-nor", "mediatek,mt81xx-nor";
mt81xx-nor is a bogus compatible string, and DT binding maintainers
will not accept it. They don't want compatible strings with "wildcards".
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-01-17 3:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 7:13 [PATCH v1 0/2] add nor flash node for mt2701 Guochun Mao
2017-01-13 7:13 ` [PATCH v1 1/2] Documentation: mtk-quadspi: update DT bindings Guochun Mao
2017-01-13 14:13 ` Boris Brezillon
2017-01-18 22:08 ` Rob Herring
2017-01-13 7:13 ` [PATCH v1 2/2] arm: dts: mt2701: add nor flash node Guochun Mao
2017-01-13 12:49 ` Marek Vasut
2017-01-13 14:17 ` Boris Brezillon
2017-01-13 15:12 ` Matthias Brugger
2017-01-13 15:21 ` Boris Brezillon
2017-01-13 16:13 ` Marek Vasut
2017-01-13 16:28 ` Boris Brezillon
2017-01-13 16:44 ` Marek Vasut
2017-01-13 16:56 ` Boris Brezillon
2017-01-13 17:33 ` Marek Vasut
2017-01-14 8:29 ` Boris Brezillon
2017-01-15 0:23 ` Marek Vasut
2017-01-16 8:40 ` Boris Brezillon
2017-01-16 16:09 ` Marek Vasut
2017-01-17 3:36 ` Thomas Petazzoni
2017-01-18 22:20 ` Rob Herring
2017-01-18 23:38 ` Thomas Petazzoni
2017-01-19 2:51 ` Rob Herring
2017-01-19 8:14 ` Boris Brezillon
2017-01-19 14:18 ` Rob Herring
2017-01-22 2:36 ` Guochun Mao
2017-01-24 10:31 ` Boris Brezillon
2017-01-24 10:38 ` John Crispin
2017-01-19 7:53 ` Boris Brezillon
2017-01-17 3:32 ` Thomas Petazzoni [this message]
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=20170117143208.03c9af83@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=guochun.mao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
/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).