From: Paul Walmsley <pjw@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the risc-v tree
Date: Mon, 8 Jun 2026 10:51:29 -0600 (MDT) [thread overview]
Message-ID: <29ca7e5e-5298-34f8-a117-48e1d80b7fe6@kernel.org> (raw)
In-Reply-To: <aiagvVcftjZXyt40@sirena.org.uk>
On Mon, 8 Jun 2026, Mark Brown wrote:
> Hi all,
>
> The following commits are also in the risc-v-fixes tree as different
> commits (but the same patches):
>
> aad60bdd0b5a6 ("riscv: Fix fast_unaligned_access_speed_key not getting initialized")
This, and the manual merge issues mentioned earlier, were caused when I
moved some patches out of the fixes branch into for-next, but didn't
update the fixes branch on k.org. Should be fixed now; sorry for the
noise.
- Paul
next prev parent reply other threads:[~2026-06-08 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 11:00 linux-next: duplicate patches in the risc-v tree Mark Brown
2026-06-08 16:51 ` Paul Walmsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-29 20:56 Stephen Rothwell
2023-10-30 18:15 ` Palmer Dabbelt
2023-10-30 19:42 ` Samuel Holland
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=29ca7e5e-5298-34f8-a117-48e1d80b7fe6@kernel.org \
--to=pjw@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox