From: Rob Herring <robh@kernel.org>
To: arinc9.unal@gmail.com
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
linux-mediatek@lists.infradead.org, linux-mips@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Sean Wang" <sean.wang@kernel.org>,
"William Dean" <williamsukatube@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Daniel Santos" <daniel.santos@pobox.com>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Landen Chao" <Landen.Chao@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>,
"Sean Wang" <sean.wang@mediatek.com>,
erkin.bozoglu@xeront.com
Subject: Re: [PATCH 08/20] dt-bindings: pinctrl: ralink: add new compatible strings
Date: Wed, 8 Mar 2023 15:00:17 -0600 [thread overview]
Message-ID: <20230308210017.GA3744272-robh@kernel.org> (raw)
In-Reply-To: <20230303002850.51858-9-arinc.unal@arinc9.com>
On Fri, Mar 03, 2023 at 03:28:37AM +0300, arinc9.unal@gmail.com wrote:
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> Add the new mediatek compatible strings. Change the compatible string on
> the examples with the mediatek compatible strings.
>
> Add the new compatible strings for mt7620, mt76x8, and rt305x to be able to
> properly document the pin muxing information of each SoC, or SoCs that use
> the same pinmux data.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> .../devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml | 7 +++++--
> .../devicetree/bindings/pinctrl/ralink,mt7621-pinctrl.yaml | 6 ++++--
> .../devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml | 5 ++++-
> 3 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> index cde6de77e228..a94d2e7a5f37 100644
> --- a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -17,7 +17,10 @@ description:
>
> properties:
> compatible:
> - const: ralink,mt7620-pinctrl
> + enum:
> + - mediatek,mt7620-pinctrl
> + - mediatek,mt76x8-pinctrl
> + - ralink,mt7620-pinctrl
To repeat the options from last time:
>Carrying both strings is a NAK. Either you (and everyone using
>these platforms) care about the ABI and are stuck with the "wrong"
>string. In the end, they are just unique identifiers. Or you don't care
>and break the ABI and rename everything. If you do that, do just that
>in your patches and make it crystal clear in the commit msg that is
>your intention and why that is okay.
Marketing/acquistion renames was just an example and common reason. That
doesn't make other reasons okay. I don't see any reason given here.
If you want to break the ABI (do you??, because the commit message
still doesn't say), then you don't need "ralink,mt7620-pinctrl".
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: arinc9.unal@gmail.com
Cc: devicetree@vger.kernel.org, "Sean Wang" <sean.wang@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Daniel Santos" <daniel.santos@pobox.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Sean Wang" <sean.wang@kernel.org>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
"William Dean" <williamsukatube@gmail.com>,
linux-mediatek@lists.infradead.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Daniel Golle" <daniel@makrotopia.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Landen Chao" <Landen.Chao@mediatek.com>,
erkin.bozoglu@xeront.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 08/20] dt-bindings: pinctrl: ralink: add new compatible strings
Date: Wed, 8 Mar 2023 15:00:17 -0600 [thread overview]
Message-ID: <20230308210017.GA3744272-robh@kernel.org> (raw)
In-Reply-To: <20230303002850.51858-9-arinc.unal@arinc9.com>
On Fri, Mar 03, 2023 at 03:28:37AM +0300, arinc9.unal@gmail.com wrote:
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> Add the new mediatek compatible strings. Change the compatible string on
> the examples with the mediatek compatible strings.
>
> Add the new compatible strings for mt7620, mt76x8, and rt305x to be able to
> properly document the pin muxing information of each SoC, or SoCs that use
> the same pinmux data.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> .../devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml | 7 +++++--
> .../devicetree/bindings/pinctrl/ralink,mt7621-pinctrl.yaml | 6 ++++--
> .../devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml | 5 ++++-
> 3 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> index cde6de77e228..a94d2e7a5f37 100644
> --- a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -17,7 +17,10 @@ description:
>
> properties:
> compatible:
> - const: ralink,mt7620-pinctrl
> + enum:
> + - mediatek,mt7620-pinctrl
> + - mediatek,mt76x8-pinctrl
> + - ralink,mt7620-pinctrl
To repeat the options from last time:
>Carrying both strings is a NAK. Either you (and everyone using
>these platforms) care about the ABI and are stuck with the "wrong"
>string. In the end, they are just unique identifiers. Or you don't care
>and break the ABI and rename everything. If you do that, do just that
>in your patches and make it crystal clear in the commit msg that is
>your intention and why that is okay.
Marketing/acquistion renames was just an example and common reason. That
doesn't make other reasons okay. I don't see any reason given here.
If you want to break the ABI (do you??, because the commit message
still doesn't say), then you don't need "ralink,mt7620-pinctrl".
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: arinc9.unal@gmail.com
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
linux-mediatek@lists.infradead.org, linux-mips@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Sean Wang" <sean.wang@kernel.org>,
"William Dean" <williamsukatube@gmail.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Daniel Santos" <daniel.santos@pobox.com>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Landen Chao" <Landen.Chao@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>,
"Sean Wang" <sean.wang@mediatek.com>,
erkin.bozoglu@xeront.com
Subject: Re: [PATCH 08/20] dt-bindings: pinctrl: ralink: add new compatible strings
Date: Wed, 8 Mar 2023 15:00:17 -0600 [thread overview]
Message-ID: <20230308210017.GA3744272-robh@kernel.org> (raw)
In-Reply-To: <20230303002850.51858-9-arinc.unal@arinc9.com>
On Fri, Mar 03, 2023 at 03:28:37AM +0300, arinc9.unal@gmail.com wrote:
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> Add the new mediatek compatible strings. Change the compatible string on
> the examples with the mediatek compatible strings.
>
> Add the new compatible strings for mt7620, mt76x8, and rt305x to be able to
> properly document the pin muxing information of each SoC, or SoCs that use
> the same pinmux data.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> .../devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml | 7 +++++--
> .../devicetree/bindings/pinctrl/ralink,mt7621-pinctrl.yaml | 6 ++++--
> .../devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml | 5 ++++-
> 3 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> index cde6de77e228..a94d2e7a5f37 100644
> --- a/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/ralink,mt7620-pinctrl.yaml
> @@ -17,7 +17,10 @@ description:
>
> properties:
> compatible:
> - const: ralink,mt7620-pinctrl
> + enum:
> + - mediatek,mt7620-pinctrl
> + - mediatek,mt76x8-pinctrl
> + - ralink,mt7620-pinctrl
To repeat the options from last time:
>Carrying both strings is a NAK. Either you (and everyone using
>these platforms) care about the ABI and are stuck with the "wrong"
>string. In the end, they are just unique identifiers. Or you don't care
>and break the ABI and rename everything. If you do that, do just that
>in your patches and make it crystal clear in the commit msg that is
>your intention and why that is okay.
Marketing/acquistion renames was just an example and common reason. That
doesn't make other reasons okay. I don't see any reason given here.
If you want to break the ABI (do you??, because the commit message
still doesn't say), then you don't need "ralink,mt7620-pinctrl".
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-08 21:00 UTC|newest]
Thread overview: 195+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 0:28 [PATCH 00/20] pinctrl: ralink: fix ABI, improve driver, move to mediatek, improve dt-bindings arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 01/20] pinctrl: ralink: reintroduce ralink,rt2880-pinmux compatible string arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:01 ` Sergio Paracuellos
2023-03-03 6:01 ` Sergio Paracuellos
2023-03-03 6:01 ` Sergio Paracuellos
2023-03-03 0:28 ` [PATCH 02/20] pinctrl: ralink: {mt7620,mt7621}: add new mediatek compatible strings arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 0:28 ` [PATCH 03/20] pinctrl: ralink: rt305x: add new compatible string for every SoC arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 6:02 ` Sergio Paracuellos
2023-03-03 0:28 ` [PATCH 04/20] pinctrl: ralink: mt7620: split out to mt76x8 arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:03 ` Sergio Paracuellos
2023-03-03 6:03 ` Sergio Paracuellos
2023-03-03 6:03 ` Sergio Paracuellos
2023-03-03 6:04 ` Sergio Paracuellos
2023-03-03 6:04 ` Sergio Paracuellos
2023-03-03 6:04 ` Sergio Paracuellos
2023-03-03 7:53 ` Arınç ÜNAL
2023-03-03 7:53 ` Arınç ÜNAL
2023-03-03 7:53 ` Arınç ÜNAL
2023-03-03 8:06 ` Sergio Paracuellos
2023-03-03 8:06 ` Sergio Paracuellos
2023-03-03 8:06 ` Sergio Paracuellos
2023-03-03 0:28 ` [PATCH 05/20] pinctrl: ralink: move to mediatek as mtmips arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:17 ` Sergio Paracuellos
2023-03-03 6:17 ` Sergio Paracuellos
2023-03-03 6:17 ` Sergio Paracuellos
2023-03-03 6:34 ` Sergio Paracuellos
2023-03-03 6:34 ` Sergio Paracuellos
2023-03-03 6:34 ` Sergio Paracuellos
2023-03-03 8:15 ` Arınç ÜNAL
2023-03-03 8:15 ` Arınç ÜNAL
2023-03-03 8:15 ` Arınç ÜNAL
2023-03-03 10:57 ` Sergio Paracuellos
2023-03-03 10:57 ` Sergio Paracuellos
2023-03-03 10:57 ` Sergio Paracuellos
2023-03-03 14:17 ` Arınç ÜNAL
2023-03-03 14:17 ` Arınç ÜNAL
2023-03-03 14:17 ` Arınç ÜNAL
2023-03-06 14:07 ` Sergio Paracuellos
2023-03-06 14:07 ` Sergio Paracuellos
2023-03-06 14:07 ` Sergio Paracuellos
2023-03-06 15:05 ` Arınç ÜNAL
2023-03-06 15:05 ` Arınç ÜNAL
2023-03-06 15:05 ` Arınç ÜNAL
2023-03-06 16:15 ` Sergio Paracuellos
2023-03-06 16:15 ` Sergio Paracuellos
2023-03-06 16:15 ` Sergio Paracuellos
2023-03-06 16:43 ` Arınç ÜNAL
2023-03-06 16:43 ` Arınç ÜNAL
2023-03-06 16:43 ` Arınç ÜNAL
2023-03-03 0:28 ` [PATCH 06/20] pinctrl: mediatek: remove OF_GPIO as reverse dependency arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:18 ` Sergio Paracuellos
2023-03-03 6:18 ` Sergio Paracuellos
2023-03-03 6:18 ` Sergio Paracuellos
2023-03-03 0:28 ` [PATCH 07/20] dt-bindings: pinctrl: ralink: improve bindings arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 20:42 ` Rob Herring
2023-03-08 20:42 ` Rob Herring
2023-03-08 20:42 ` Rob Herring
2023-03-03 0:28 ` [PATCH 08/20] dt-bindings: pinctrl: ralink: add new compatible strings arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:00 ` Rob Herring [this message]
2023-03-08 21:00 ` Rob Herring
2023-03-08 21:00 ` Rob Herring
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-09 9:48 ` Krzysztof Kozlowski
2023-03-09 9:48 ` Krzysztof Kozlowski
2023-03-09 9:48 ` Krzysztof Kozlowski
2023-03-03 0:28 ` [PATCH 09/20] dt-bindings: pinctrl: ralink: {mt7620,mt7621}: rename to mediatek arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:05 ` Rob Herring
2023-03-08 21:05 ` Rob Herring
2023-03-08 21:05 ` Rob Herring
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-08 21:19 ` Arınç ÜNAL
2023-03-09 7:53 ` Arınç ÜNAL
2023-03-09 7:53 ` Arınç ÜNAL
2023-03-09 7:53 ` Arınç ÜNAL
2023-03-09 9:52 ` Krzysztof Kozlowski
2023-03-09 9:52 ` Krzysztof Kozlowski
2023-03-09 9:52 ` Krzysztof Kozlowski
2023-03-09 10:34 ` Arınç ÜNAL
2023-03-09 10:34 ` Arınç ÜNAL
2023-03-09 10:34 ` Arınç ÜNAL
2023-03-09 11:33 ` Sergio Paracuellos
2023-03-09 11:33 ` Sergio Paracuellos
2023-03-09 11:33 ` Sergio Paracuellos
2023-03-09 21:08 ` Arınç ÜNAL
2023-03-09 21:08 ` Arınç ÜNAL
2023-03-09 21:08 ` Arınç ÜNAL
2023-03-10 7:05 ` Sergio Paracuellos
2023-03-10 7:05 ` Sergio Paracuellos
2023-03-10 7:05 ` Sergio Paracuellos
2023-03-10 7:45 ` Arınç ÜNAL
2023-03-10 7:45 ` Arınç ÜNAL
2023-03-10 7:45 ` Arınç ÜNAL
2023-03-03 0:28 ` [PATCH 10/20] dt-bindings: pinctrl: mediatek: mt6795: rename to mediatek,mt6795-pinctrl arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 11/20] dt-bindings: pinctrl: mediatek: mt8186: rename to mediatek,mt8186-pinctrl arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 12/20] dt-bindings: pinctrl: mediatek: mt8192: rename to mediatek,mt8192-pinctrl arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 13/20] dt-bindings: pinctrl: mediatek: mt8195: rename to mediatek,mt8195-pinctrl arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 14/20] dt-bindings: pinctrl: mediatek: fix naming inconsistency arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:05 ` Rob Herring
2023-03-08 21:05 ` Rob Herring
2023-03-08 21:05 ` Rob Herring
2023-03-03 0:28 ` [PATCH 15/20] dt-bindings: pinctrl: {mediatek,ralink}: fix formatting arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:11 ` Rob Herring
2023-03-08 21:11 ` Rob Herring
2023-03-08 21:11 ` Rob Herring
2023-03-08 21:30 ` Arınç ÜNAL
2023-03-08 21:30 ` Arınç ÜNAL
2023-03-08 21:30 ` Arınç ÜNAL
2023-03-03 0:28 ` [PATCH 16/20] dt-bindings: pinctrl: mediatek: drop quotes from referred schemas arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` [PATCH 17/20] dt-bindings: pinctrl: mediatek: mt7986: fix patternProperties regex arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:15 ` Rob Herring
2023-03-08 21:15 ` Rob Herring
2023-03-08 21:15 ` Rob Herring
2023-03-08 21:22 ` Arınç ÜNAL
2023-03-08 21:22 ` Arınç ÜNAL
2023-03-08 21:22 ` Arınç ÜNAL
2023-03-03 0:28 ` [PATCH 18/20] dt-bindings: pinctrl: ralink: rt305x: split binding arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:17 ` Rob Herring
2023-03-08 21:17 ` Rob Herring
2023-03-08 21:17 ` Rob Herring
2023-03-03 0:28 ` [PATCH 19/20] dt-bindings: pinctrl: mediatek: mt7620: " arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-08 21:22 ` Rob Herring
2023-03-08 21:22 ` Rob Herring
2023-03-08 21:22 ` Rob Herring
2023-03-09 9:54 ` Krzysztof Kozlowski
2023-03-09 9:54 ` Krzysztof Kozlowski
2023-03-09 9:54 ` Krzysztof Kozlowski
2023-03-09 21:03 ` Arınç ÜNAL
2023-03-09 21:03 ` Arınç ÜNAL
2023-03-09 21:03 ` Arınç ÜNAL
2023-03-03 0:28 ` [PATCH 20/20] MAINTAINERS: move ralink pinctrl to mediatek mips pinctrl arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 0:28 ` arinc9.unal
2023-03-03 6:21 ` Sergio Paracuellos
2023-03-03 6:21 ` Sergio Paracuellos
2023-03-03 6:21 ` Sergio Paracuellos
2023-03-06 13:50 ` [PATCH 00/20] pinctrl: ralink: fix ABI, improve driver, move to mediatek, improve dt-bindings Linus Walleij
2023-03-06 13:50 ` Linus Walleij
2023-03-06 13:50 ` Linus Walleij
2023-03-06 14:17 ` Sergio Paracuellos
2023-03-06 14:17 ` Sergio Paracuellos
2023-03-06 14:17 ` Sergio Paracuellos
2023-03-06 14:55 ` Arınç ÜNAL
2023-03-06 14:55 ` Arınç ÜNAL
2023-03-06 14:55 ` Arınç ÜNAL
2023-03-06 22:09 ` Linus Walleij
2023-03-06 22:09 ` Linus Walleij
2023-03-06 22:09 ` 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=20230308210017.GA3744272-robh@kernel.org \
--to=robh@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=arinc.unal@arinc9.com \
--cc=arinc9.unal@gmail.com \
--cc=daniel.santos@pobox.com \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.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=linux-mips@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sergio.paracuellos@gmail.com \
--cc=williamsukatube@gmail.com \
/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.