From: Rob Herring <robh@kernel.org>
To: sean.wang@mediatek.com
Cc: matthias.bgg@gmail.com, rjw@rjwysocki.net, khilman@baylibre.com,
ulf.hansson@linaro.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: soc: add header files required for MT7623A SCPSYS dt-binding
Date: Mon, 12 Feb 2018 08:44:01 -0600 [thread overview]
Message-ID: <20180212144401.yzrecztdveua3zix@rob-hp-laptop> (raw)
In-Reply-To: <9955178588f8bde01782d0645b25a7b24cceb87b.1517998367.git.sean.wang@mediatek.com>
On Wed, Feb 07, 2018 at 06:22:48PM +0800, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Add relevant header files required for dt-bindings of SCPSYS power domain
> control for subsystems found on MT7623A SoC.
>
> v1 -> v2: fix typos and treat the patch as a dt-binding patch
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> Cc: Rob Herring <robh@kernel.org>
> ---
> include/dt-bindings/power/mt7623a-power.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
> create mode 100644 include/dt-bindings/power/mt7623a-power.h
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-02-12 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 10:22 [PATCH v2 1/4] dt-bindings: soc: add SCPSYS binding for MT7623 and MT7623A SoC sean.wang
2018-02-07 10:22 ` [PATCH v2 2/4] dt-bindings: soc: add header files required for MT7623A SCPSYS dt-binding sean.wang
2018-02-12 14:44 ` Rob Herring [this message]
2018-02-07 10:22 ` [PATCH v2 3/4] soc: mediatek: avoid hardcoded value with bus_prot_mask sean.wang
2018-02-07 10:22 ` [PATCH v2 4/4] soc: mediatek: add SCPSYS power domain driver for MediaTek MT7623A SoC sean.wang
2018-02-07 20:19 ` [PATCH v2 1/4] dt-bindings: soc: add SCPSYS binding for MT7623 and " Ulf Hansson
2018-03-07 9:17 ` Sean Wang
2018-03-11 22:44 ` Matthias Brugger
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=20180212144401.yzrecztdveua3zix@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=sean.wang@mediatek.com \
--cc=ulf.hansson@linaro.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).