From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Corbet <corbet@lwn.net>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the jc_docs tree
Date: Fri, 14 Feb 2025 16:10:32 +1100 [thread overview]
Message-ID: <20250214161032.1ef4902e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
Hi all,
The following commit is also in the risc-v-fixes tree as a different
commit (but the same patch):
b48e0f696b71 ("Documentation: riscv: Remove KPROBES_ON_FTRACE")
This is commit
ccc71244f95c ("Documentation: riscv: Remove KPROBES_ON_FTRACE")
in the risc-v-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-02-14 5:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 5:10 Stephen Rothwell [this message]
2025-02-14 13:20 ` linux-next: duplicate patch in the jc_docs tree Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 1:25 Stephen Rothwell
2025-05-07 1:19 Stephen Rothwell
2025-05-07 6:51 ` Jonathan Corbet
2025-05-07 1:18 Stephen Rothwell
2025-02-19 0:32 Stephen Rothwell
2025-01-17 1:02 Stephen Rothwell
2024-10-14 2:03 Stephen Rothwell
2024-10-14 14:52 ` Jonathan Corbet
2024-02-13 4:49 Stephen Rothwell
2024-02-13 14:36 ` Jonathan Corbet
2024-02-12 23:37 Stephen Rothwell
2024-02-12 23:41 ` Jonathan Corbet
2023-04-11 5:16 Stephen Rothwell
2023-04-11 22:16 ` Jonathan Corbet
2023-01-13 0:11 Stephen Rothwell
2023-01-13 16:29 ` Jonathan Corbet
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=20250214161032.1ef4902e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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