From: Arnd Bergmann <arnd@arndb.de>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] Update UniPhier armv8 devicetree
Date: Sat, 30 Jul 2022 14:03:06 +0200 [thread overview]
Message-ID: <CAK8P3a0egd9dupLFid9CsSygQyTK3KopB8m5LVgnUW9L1cF6JA@mail.gmail.com> (raw)
In-Reply-To: <0a0a64a7-60cc-e95d-c2e3-3c11a53a6527@socionext.com>
On Fri, Jul 29, 2022 at 11:52 AM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
> On 2022/07/04 9:21, Kunihiko Hayashi wrote:
> > Update devicetree sources for UniPhier armv8 SoCs to remove dtschema
> > warnings, add support existing features that haven't yet been
> > described, and replace constants with macros.
>
> If there is nothing wrong with this series and armv7 DT series,
> I'd like to make a pull request.
> If the request is late, carry it over to the next version.
>
> How about that?
The timing is not great, as normal updates should get merged as parts
of the normal
pull requests, which I have already sent.
A lot of the changes can be considered bugfixes, and I would still
merge them if you
think they are harmless and can fix things. In this case, also mark them as
'Cc: stable@vger.kernel.org' to be backported into lts kernels. Anything that
does not qualify as a bugfix should now go into the 5.21 merge window.
Please send the bugfix pull request as soon as you can so we can merge that
early. The other updates should be rebased onto v5.20-rc1 once that is
released in about two weeks.
Arnd
next prev parent reply other threads:[~2022-07-30 12:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 0:21 [PATCH 0/9] Update UniPhier armv8 devicetree Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 1/9] arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 2/9] arm64: dts: uniphier: Rename pvtctl node to thermal-sensor Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 3/9] arm64: dts: uniphier: Rename usb-phy node to usb-glue Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 4/9] arm64: dts: uniphier: Rename gpio-hog nodes Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 5/9] arm64: dts: uniphier: Use GIC interrupt definitions Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 6/9] arm64: dts: uniphier: Add ahci controller and glue layer nodes for PXs3 Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 7/9] arm64: dts: uniphier: Add USB-device support for PXs3 reference board Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 8/9] arm64: dts: uniphier: Fix opp-table node name for LD20 Kunihiko Hayashi
2022-07-04 0:21 ` [PATCH 9/9] arm64: dts: uniphier: Remove compatible "snps,dw-pcie" from pcie node Kunihiko Hayashi
2022-07-29 9:52 ` [PATCH 0/9] Update UniPhier armv8 devicetree Kunihiko Hayashi
2022-07-30 12:03 ` Arnd Bergmann [this message]
2022-08-02 13:24 ` Kunihiko Hayashi
2022-08-02 13:55 ` 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=CAK8P3a0egd9dupLFid9CsSygQyTK3KopB8m5LVgnUW9L1cF6JA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=olof@lixom.net \
--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).