From: Rob Herring <robh@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: linux-mips@vger.kernel.org, Paul Burton <paul.burton@mips.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4 v4] dt-bindings: mips: Add gardena vendor prefix and board description
Date: Tue, 27 Aug 2019 10:32:46 -0500 [thread overview]
Message-ID: <20190827153246.GA3678@bogus> (raw)
In-Reply-To: <20190812103655.11070-3-sr@denx.de>
On Mon, 12 Aug 2019 12:36:54 +0200, Stefan Roese wrote:
> This patch adds the vendor prefix for gardena and a short description
> including the compatible string for the "GARDENA smart Gateway" based
> on the MT7688 SoC.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Paul Burton <paul.burton@mips.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> ---
> v4:
> - Move board description into ralink.txt instead of creating a gardena
> board file (Rob)
> - Slightly changed board compatible
>
> v3:
> - New patch
>
> Documentation/devicetree/bindings/mips/ralink.txt | 13 +++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 2 files changed, 15 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-08-27 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 10:36 [PATCH 1/4 v4] MIPS: ralink: mt7628a.dtsi: Add I2C controller DT node Stefan Roese
2019-08-12 10:36 ` [PATCH 2/4 v4] dt-bindings: mips: Add missing mt7688a-soc compatible Stefan Roese
2019-08-27 15:32 ` Rob Herring
2019-08-12 10:36 ` [PATCH 3/4 v4] dt-bindings: mips: Add gardena vendor prefix and board description Stefan Roese
2019-08-27 15:32 ` Rob Herring [this message]
2019-08-12 10:36 ` [PATCH 4/4 v4] MIPS: ralink: Add GARDENA smart Gateway MT7688 board Stefan Roese
2019-10-07 17:51 ` [PATCH 1/4 v4] MIPS: ralink: mt7628a.dtsi: Add I2C controller DT node Paul Burton
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=20190827153246.GA3678@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=sr@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.