From: Arnd Bergmann <arnd@kernel.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
SoC Team <soc@kernel.org>, Olof Johansson <olof@lixom.net>,
Willy Tarreau <w@1wt.eu>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7
Date: Wed, 9 Dec 2020 22:40:48 +0100 [thread overview]
Message-ID: <CAK8P3a2Kokj+fgRPGcSCcSW8x2=4_P1LJqmBp09_QtBRD0yf4w@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0KHiO0Xis9+hiJa7uDZET9xzf7wRExxZXBUFXeAEMXqQ@mail.gmail.com>
On Wed, Dec 9, 2020 at 5:47 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Mon, Dec 7, 2020 at 11:55 AM Daniel Palmer <daniel@0x0f.com> wrote:
> >
> > Hi Linus,
> >
> > On Sun, 6 Dec 2020 at 06:43, Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > > OK finished!
> > > Patches 1, 2 & 3 applied to the GPIO tree for v5.11.
> >
> > Awesome! Thank you Linus. :)
> >
> > Arnd and Olof: Sorry for being a noob.. Is there anything I need to do
> > for patches 4 and 5 (device tree bits)?
> > They are in the Linux SoC patchwork.
>
> I've picked them up from there along with the second series of DT changes.
And I made a mess, as I had not realized that the DT patches depend on
the dt-binding header. I've applied that patch on top now to make my
branch build cleanly again, even though it is not fully bisectable.
Arnd
_______________________________________________
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:[~2020-12-09 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 11:07 [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7 Daniel Palmer
2020-11-29 11:07 ` [PATCH v4 1/5] dt-bindings: gpio: Add a binding header for the MSC313 GPIO driver Daniel Palmer
2020-11-29 11:07 ` [PATCH v4 2/5] dt-bindings: gpio: Binding for MStar MSC313 GPIO controller Daniel Palmer
2020-12-01 2:02 ` Rob Herring
2020-11-29 11:08 ` [PATCH v4 3/5] gpio: msc313: MStar MSC313 GPIO driver Daniel Palmer
2020-12-09 21:58 ` Arnd Bergmann
2020-12-10 10:29 ` Daniel Palmer
2020-12-10 14:27 ` Arnd Bergmann
2020-12-10 15:49 ` Daniel Palmer
2020-12-10 20:22 ` Arnd Bergmann
2020-12-10 14:23 ` Andy Shevchenko
2020-12-10 15:21 ` Daniel Palmer
2020-11-29 11:08 ` [PATCH v4 4/5] ARM: mstar: Add gpio controller to MStar base dtsi Daniel Palmer
2020-11-29 11:08 ` [PATCH v4 5/5] ARM: mstar: Fill in GPIO controller properties for infinity Daniel Palmer
2020-12-05 21:42 ` [PATCH v4 0/5] Add GPIO support for MStar/SigmaStar ARMv7 Linus Walleij
2020-12-07 10:55 ` Daniel Palmer
2020-12-09 16:47 ` Arnd Bergmann
2020-12-09 21:40 ` Arnd Bergmann [this message]
2020-12-09 20:30 ` Arnd Bergmann
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='CAK8P3a2Kokj+fgRPGcSCcSW8x2=4_P1LJqmBp09_QtBRD0yf4w@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.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=olof@lixom.net \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
--cc=w@1wt.eu \
/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).