From: Palmer Dabbelt <palmer@dabbelt.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: linux-next: duplicate patch in the risc-v tree
Date: Sun, 28 Apr 2024 14:55:36 -0700 (PDT) [thread overview]
Message-ID: <mhng-24fa846c-974e-452c-a593-2206e8970851@palmer-ri-x1c9> (raw)
In-Reply-To: <20240429073553.503958e8@canb.auug.org.au>
On Sun, 28 Apr 2024 14:35:53 PDT (-0700), Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patch):
>
> bac292e849d7 ("selftests: sud_test: return correct emulated syscall value on RISC-V")
>
> This is commit
>
> 17c67ed752d6 ("selftests: sud_test: return correct emulated syscall value on RISC-V")
>
> in Linus' tree.
Sorry about that, looks like I accidentally merge this into both
for-next and fixes. It's a fix, though not strictly a regression (the
selftest never worked), so maybe I just was being too careful the first
time.
I dropped it from for-next.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2024-04-28 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 21:35 linux-next: duplicate patch in the risc-v tree Stephen Rothwell
2024-04-28 21:55 ` Palmer Dabbelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 22:06 Stephen Rothwell
2024-04-11 19:57 ` Palmer Dabbelt
2023-11-02 20:58 Stephen Rothwell
2023-11-02 21:07 ` Palmer Dabbelt
2023-10-29 23:12 Stephen Rothwell
2023-08-30 22:01 Stephen Rothwell
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=mhng-24fa846c-974e-452c-a593-2206e8970851@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
/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).