linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: John Crispin <blogic@openwrt.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: mediatek: Modify pinctrl bindings for mt7623
Date: Wed, 20 Jan 2016 17:34:54 +0800	[thread overview]
Message-ID: <1453282494.16515.10.camel@mtksdaap41> (raw)
In-Reply-To: <1452441608-24176-1-git-send-email-blogic@openwrt.org>

On Sun, 2016-01-10 at 17:00 +0100, John Crispin wrote:
> Signed-off-by: John Crispin <blogic@openwrt.org>
> ---
>  Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> index 9ffb0b2..4fa4444 100644
> --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> @@ -5,6 +5,7 @@ The Mediatek's Pin controller is used to control SoC pins.
>  Required properties:
>  - compatible: value should be one of the following.
>  	"mediatek,mt2701-pinctrl", compatible with mt2701 pinctrl.
> +	"mediatek,mt7623-pinctrl", compatible with mt7623 pinctrl.
>  	"mediatek,mt6397-pinctrl", compatible with mt6397 pinctrl.
>  	"mediatek,mt8127-pinctrl", compatible with mt8127 pinctrl.
>  	"mediatek,mt8135-pinctrl", compatible with mt8135 pinctrl.

Hi John,

Please keep the list sorted.

Joe.C



      parent reply	other threads:[~2016-01-20  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 16:00 [PATCH 1/2] dt-bindings: mediatek: Modify pinctrl bindings for mt7623 John Crispin
2016-01-10 16:00 ` [PATCH 2/2] pinctrl: mediatek: Add pinctrl files for MT7623 John Crispin
2016-01-10 16:40   ` John Crispin
2016-01-20  9:41   ` Yingjoe Chen
2016-01-20  9:34 ` Yingjoe Chen [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=1453282494.16515.10.camel@mtksdaap41 \
    --to=yingjoe.chen@mediatek.com \
    --cc=blogic@openwrt.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.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).