devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexey Romanov <avromanov@sberdevices.ru>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	khilman@baylibre.com, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@sberdevices.ru
Subject: Re: [PATCH v1 1/3] meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM
Date: Mon, 6 Mar 2023 14:49:55 +0100	[thread overview]
Message-ID: <2d9e01df-0047-98bc-f1e7-fa860d92c254@linaro.org> (raw)
In-Reply-To: <CACRpkdbWubk3A3qYuYqDc4OBGP6T7TaKwFeW17CwAzPvttk=WQ@mail.gmail.com>

Hi Linus,

On 06/03/2023 14:45, Linus Walleij wrote:
> On Wed, Feb 22, 2023 at 12:50 PM Alexey Romanov
> <avromanov@sberdevices.ru> wrote:
> 
>> Tested A1 pinctrl support for ARM and it works.
>>
>> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> 
> This patch applied to the pinctrl tree for v6.4.

Erf, this serie is something we would avoid, so no need to apply it for v6.4

> 
> Have you considered also adding || COMPILE_TEST?

It would be great to have || COMPILE_TEST for sure

Neil

> 
> Or does that break builds?
> 
> Yours,
> Linus Walleij


  reply	other threads:[~2023-03-06 13:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 11:50 [PATCH v1 0/3] Meson A1 32-bit support Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 1/3] meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM Alexey Romanov
2023-03-06 13:45   ` Linus Walleij
2023-03-06 13:49     ` neil.armstrong [this message]
2023-03-06 13:52       ` Linus Walleij
2023-02-22 11:50 ` [PATCH v1 2/3] firmware: meson: use CONFIG_MESON_SM " Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 3/3] arch/arm: dts: introduce meson-a1 device tree Alexey Romanov
2023-02-23  9:08   ` Krzysztof Kozlowski
2023-02-23  9:09     ` Krzysztof Kozlowski
2023-02-27 14:39       ` Dmitry Rokosov
2023-02-27 14:41         ` Krzysztof Kozlowski
2023-02-27  8:15 ` [PATCH v1 0/3] Meson A1 32-bit support neil.armstrong
2023-02-27 14:28   ` Dmitry Rokosov
2023-02-27 14:46     ` neil.armstrong
2023-02-27 16:01       ` Dmitry Rokosov
2023-02-27 14:58     ` Arnd Bergmann
2023-02-27 15:51       ` Dmitry Rokosov
2023-02-27 16:15         ` Arnd Bergmann
2023-02-27 16:37           ` Dmitry Rokosov
2023-02-27 16:38           ` Neil Armstrong
2023-02-27 16:50             ` Dmitry Rokosov
2023-02-27 18:19               ` Arnd Bergmann
2023-02-28  8:49                 ` Dmitry Rokosov
2023-03-09 21:52                   ` Kevin Hilman
2023-03-10 15:20                     ` Dmitry Rokosov

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=2d9e01df-0047-98bc-f1e7-fa860d92c254@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=avromanov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=robh+dt@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).