From: Linus Walleij <linus.walleij@linaro.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
Phil Elwell <phil@raspberrypi.com>,
Kent Gibson <warthog618@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 0/2] pinctrl: bcm2835: persist_gpio_outputs follow-up
Date: Mon, 17 Jun 2024 09:51:38 +0200 [thread overview]
Message-ID: <CACRpkdZd8-C2uuR4f0T7a19V6KsurUWUXEqYR94HUt1jrT_7+A@mail.gmail.com> (raw)
In-Reply-To: <20240603181938.76047-1-wahrenst@gmx.net>
On Mon, Jun 3, 2024 at 8:20 PM Stefan Wahren <wahrenst@gmx.net> wrote:
> After the patch "pinctrl: bcm2835: Make pin freeing behavior configurable"
> has been applied for 6.10-rc1, Andy Shevchenko submitted two comments [1].
> So this small series address them.
>
> [1] - https://lore.kernel.org/linux-gpio/Zjk-C0nLmlynqLAE@surfacebook.localdomain/
>
> Stefan Wahren (2):
> pinctrl: bcm2835: Fix permissions of persist_gpio_outputs
Applied for fixes.
> pinctrl: bcm2835: Use string_choices API instead of ternary operator
Applied for next.
Yours,
Linus Walleij
prev parent reply other threads:[~2024-06-17 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:19 [PATCH 0/2] pinctrl: bcm2835: persist_gpio_outputs follow-up Stefan Wahren
2024-06-03 18:19 ` [PATCH 1/2] pinctrl: bcm2835: Fix permissions of persist_gpio_outputs Stefan Wahren
2024-06-04 7:57 ` Florian Fainelli
2024-06-03 18:19 ` [PATCH 2/2] pinctrl: bcm2835: Use string_choices API instead of ternary operator Stefan Wahren
2024-06-04 7:28 ` Florian Fainelli
2024-06-04 7:33 ` Andy Shevchenko
2024-06-17 7:51 ` Linus Walleij [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=CACRpkdZd8-C2uuR4f0T7a19V6KsurUWUXEqYR94HUt1jrT_7+A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brgl@bgdev.pl \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.net \
--cc=warthog618@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 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).