From: Conor Dooley <conor@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, Palmer Dabbelt <palmer@dabbelt.com>,
linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V Devicetree fixes for v6.8-final
Date: Tue, 12 Mar 2024 13:09:21 +0000 [thread overview]
Message-ID: <20240312-squad-evaluate-e96191870035@spud> (raw)
In-Reply-To: <1f827492-2a68-4753-aac2-fcbdca51e460@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Mon, Mar 11, 2024 at 09:12:08AM +0100, Arnd Bergmann wrote:
> On Wed, Mar 6, 2024, at 19:08, Conor Dooley wrote:
> > Hey Arnd,
> >
> > I know it is pretty late in the day here for fixes, and I would've kept
> > the builtin dtb fix as v6.9 material, but Geert reported yesterday that
> > boot was broken on the jh7100 platforms due to a fix that I sent in my
> > last PR.
>
> Sorry I missed them last week. I added this to the soc/dt branch
> for 6.9 now. You might want to ask stable@vger.kernel.org for a
> backport after -rc1 is out if they don't automatically pick them
> up.
Right, it was an unexpected PR and late in the cycle. It's only the
jh7100 patch that'd need a backport. I'll request a backport if one
doesn't happen automagically, which it probably will, even though I
didn't have a cc: stable on it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-12 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 18:08 [GIT PULL] RISC-V Devicetree fixes for v6.8-final Conor Dooley
2024-03-11 8:12 ` Arnd Bergmann
2024-03-12 13:09 ` Conor Dooley [this message]
2024-03-11 19:50 ` patchwork-bot+linux-soc
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=20240312-squad-evaluate-e96191870035@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=soc@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 read-only IMAP folder(s) and NNTP newsgroup(s).