linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Hsin-Yi Wang <hsinyi@chromium.org>,
	Rob Herring <robh+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Enric Balletbo Serra <eballetbo@gmail.com>,
	Sean Wang <sean.wang@kernel.org>,
	Andy Teng <andy.teng@mediatek.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] arm: dts: mt8135: Move pinfunc to include/dt-bindings/pinctrl
Date: Thu, 5 Aug 2021 11:02:18 +0200	[thread overview]
Message-ID: <d48087c2-ddff-0c58-c7e6-a0ba526a393f@gmail.com> (raw)
In-Reply-To: <20210804044033.3047296-1-hsinyi@chromium.org>

Hi Linus,

On 04/08/2021 06:40, Hsin-Yi Wang wrote:
> Move mt8135-pinfunc.h into include/dt-bindings/pinctrl so that we can
> include it in yaml examples.
> 
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> ---
>  arch/arm/boot/dts/mt8135.dtsi                                   | 2 +-
>  .../boot/dts => include/dt-bindings/pinctrl}/mt8135-pinfunc.h   | 0
>  2 files changed, 1 insertion(+), 1 deletion(-)
>  rename {arch/arm/boot/dts => include/dt-bindings/pinctrl}/mt8135-pinfunc.h (100%)
> 

If that's fine with you, I'll take patch 1+2 through my tree. IMHO the best for
patch 3 would be to go through your tree.

Sounds good?

Regards,
Matthias

> diff --git a/arch/arm/boot/dts/mt8135.dtsi b/arch/arm/boot/dts/mt8135.dtsi
> index 0e4e835026db0..a031b36363187 100644
> --- a/arch/arm/boot/dts/mt8135.dtsi
> +++ b/arch/arm/boot/dts/mt8135.dtsi
> @@ -9,7 +9,7 @@
>  #include <dt-bindings/interrupt-controller/irq.h>
>  #include <dt-bindings/interrupt-controller/arm-gic.h>
>  #include <dt-bindings/reset/mt8135-resets.h>
> -#include "mt8135-pinfunc.h"
> +#include <dt-bindings/pinctrl/mt8135-pinfunc.h>
>  
>  / {
>  	#address-cells = <2>;
> diff --git a/arch/arm/boot/dts/mt8135-pinfunc.h b/include/dt-bindings/pinctrl/mt8135-pinfunc.h
> similarity index 100%
> rename from arch/arm/boot/dts/mt8135-pinfunc.h
> rename to include/dt-bindings/pinctrl/mt8135-pinfunc.h
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-08-05  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  4:40 [PATCH v4 1/3] arm: dts: mt8135: Move pinfunc to include/dt-bindings/pinctrl Hsin-Yi Wang
2021-08-04  4:40 ` [PATCH v4 2/3] arm: dts: mt8183: " Hsin-Yi Wang
2021-08-04  4:40 ` [PATCH v4 3/3] dt-bindings: mediatek: convert pinctrl to yaml Hsin-Yi Wang
2021-08-05  9:02 ` Matthias Brugger [this message]
2021-08-11  8:48   ` [PATCH v4 1/3] arm: dts: mt8135: Move pinfunc to include/dt-bindings/pinctrl Linus Walleij
2021-08-11  8:53 ` Linus Walleij

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=d48087c2-ddff-0c58-c7e6-a0ba526a393f@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=andy.teng@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eballetbo@gmail.com \
    --cc=hsinyi@chromium.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sean.wang@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).