From: Linus Walleij <linus.walleij@linaro.org>
To: Gary Bisson <gary.bisson@boundarydevices.com>
Cc: linux-amlogic@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] pinctrl: meson-g12a: add more pwm_f options
Date: Sun, 16 Jan 2022 02:03:18 +0100 [thread overview]
Message-ID: <CACRpkdZRL8VuY5K_d69VHE6eXCmUb18ZRs5v9shExe4ipmw90Q@mail.gmail.com> (raw)
In-Reply-To: <20220103154616.308376-2-gary.bisson@boundarydevices.com>
On Mon, Jan 3, 2022 at 4:46 PM Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Add missing PWM_F pin muxing for GPIOA_11 and GPIOZ_12.
>
> Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
This patch 1/3 applied for v5.18.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-01-16 1:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 15:46 [PATCH 0/3] meson-g12: add pwm and uart pin muxing options Gary Bisson
2022-01-03 15:46 ` [PATCH 1/3] pinctrl: meson-g12a: add more pwm_f options Gary Bisson
2022-01-12 8:30 ` Neil Armstrong
2022-01-16 1:03 ` Linus Walleij [this message]
2022-01-03 15:46 ` [PATCH 2/3] arm64: dts: meson-g12-common: " Gary Bisson
2022-01-12 8:30 ` Neil Armstrong
2022-01-03 15:46 ` [PATCH 3/3] arm64: dts: meson-g12-common: add uart_ao_b pins muxing Gary Bisson
2022-01-12 8:33 ` Neil Armstrong
2022-01-12 13:01 ` Gary Bisson
2022-01-12 14:34 ` Neil Armstrong
[not found] ` <20220112211642.2248901-1-gary.bisson@boundarydevices.com>
2022-01-12 21:16 ` [PATCH v2 1/3] pinctrl: meson-g12a: add more pwm_f options Gary Bisson
2022-01-12 21:16 ` [PATCH v2 2/3] arm64: dts: meson-g12-common: " Gary Bisson
2022-01-12 21:16 ` [PATCH v2 3/3] arm64: dts: meson-g12-common: add uart_ao_b pins muxing Gary Bisson
2022-01-13 8:57 ` Neil Armstrong
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=CACRpkdZRL8VuY5K_d69VHE6eXCmUb18ZRs5v9shExe4ipmw90Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gary.bisson@boundarydevices.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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 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).