From: Linus Walleij <linus.walleij@linaro.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Phil Elwell <phil@raspberrypi.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v2 1/2] pinctrl: bcm2835: Change init order for gpio hogs
Date: Tue, 4 Jan 2022 18:04:36 +0100 [thread overview]
Message-ID: <CACRpkdZCiRJ-8eN3arKgt0s5iWgGwGE=aZMo7yx7UtUn=GNF2g@mail.gmail.com> (raw)
In-Reply-To: <0951facb-8b19-c0f3-4f25-a5ac4a798859@web.de>
On Sun, Jan 2, 2022 at 4:16 PM Jan Kiszka <jan.kiszka@web.de> wrote:
> But, in fact, this series was misordered then, suggesting that patch 1
> was independent of patch 2, but it actually depended on patch 2 to avoid
> even temporary regressions.
I picked patch 2/2 out of my tree and sent it off to the SoC tree that applies
DTS fixes.
Let's see if they manage to get it to Torvalds before the merge window.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-01-04 17:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:22 [PATCH v2 0/2] pinctrl: bcm2835: Fix gpio hogs and pin reinitialisation Phil Elwell
2021-12-06 9:22 ` [PATCH v2 1/2] pinctrl: bcm2835: Change init order for gpio hogs Phil Elwell
2021-12-07 18:32 ` Florian Fainelli
2021-12-09 23:24 ` Linus Walleij
2021-12-29 19:07 ` Stefan Wahren
2021-12-29 21:11 ` Florian Fainelli
2022-01-02 6:54 ` Linus Walleij
2022-01-02 11:02 ` Jan Kiszka
2022-01-02 12:33 ` Stefan Wahren
2022-01-02 15:12 ` Jan Kiszka
2022-01-02 15:16 ` Jan Kiszka
2022-01-04 17:04 ` Linus Walleij [this message]
2021-12-06 9:22 ` [PATCH v2 2/2] ARM: dts: gpio-ranges property is now required Phil Elwell
2021-12-06 10:33 ` Linus Walleij
2021-12-06 17:24 ` Florian Fainelli
2021-12-07 15:29 ` Linus Walleij
2021-12-10 11:12 ` nicolas saenz julienne
[not found] ` <CGME20211214142139eucas1p1c100b7fd4b8c8ce85bc03e1ce6b783db@eucas1p1.samsung.com>
2021-12-14 14:21 ` Marek Szyprowski
2021-12-14 14:32 ` Phil Elwell
2021-12-14 17:12 ` Florian Fainelli
2021-12-15 9:02 ` nicolas saenz julienne
2021-12-15 17:14 ` Florian Fainelli
2021-12-16 3:27 ` Linus Walleij
2021-12-16 3:28 ` Florian Fainelli
2021-12-16 3:31 ` Linus Walleij
2021-12-16 8:28 ` nicolas saenz julienne
2021-12-15 17:15 ` Florian Fainelli
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='CACRpkdZCiRJ-8eN3arKgt0s5iWgGwGE=aZMo7yx7UtUn=GNF2g@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@web.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=treding@nvidia.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.