From: "Hawkins, Nick" <nick.hawkins@hpe.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Verdun, Jean-Marie" <verdun@hpe.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Russell King - ARM Linux" <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>, SoC Team <soc@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"Guenter Roeck" <linux@roeck-us.net>,
DTML <devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LINUXWATCHDOG <linux-watchdog@vger.kernel.org>,
Joel Stanley <joel@jms.id.au>
Subject: RE: [PATCH v8 0/8] Introduce HPE GXP Architecture
Date: Wed, 18 May 2022 13:12:41 +0000 [thread overview]
Message-ID: <DM4PR84MB192761B3970E4934D059C3F188D19@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAK8P3a0914=TM9f1CNcg_PXfHvt6nHDPyrvLp=0KO4hZM2GT5w@mail.gmail.com>
> Hi Nick,
> I have preliminarily applied this version into a the arm/late branch, but since I'm travelling at the moment, I cannot actually push that branch out for linux-next before the coming merge window.
> My feeling is that this should just wait until 5.20 now, but if you and others others feel strongly about it, I could send it during the second half of the merge window.
> It still needs to pass all the CI build tests, but at least it's unlikely that there are any runtime regressions for other platforms.
Hi Arnd,
We have a talk planned for the North America Open Source Summit (June 20-24) and it would be great if this patch set could be in Linux by then. If it is not possible we can handle that.
Thanks,
-Nick Hawkins
next prev parent reply other threads:[~2022-05-18 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 16:33 [PATCH v8 0/8] Introduce HPE GXP Architecture nick.hawkins
2022-05-18 12:13 ` Arnd Bergmann
2022-05-18 13:12 ` Hawkins, Nick [this message]
2022-05-23 10:51 ` 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=DM4PR84MB192761B3970E4934D059C3F188D19@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM \
--to=nick.hawkins@hpe.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=tglx@linutronix.de \
--cc=verdun@hpe.com \
--cc=wim@linux-watchdog.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).