From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul@pwsan.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the risc-v tree
Date: Thu, 31 Aug 2023 07:57:30 +1000 [thread overview]
Message-ID: <20230831075730.0dd941dd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
Hi all,
Commits
dbe46b094026 ("RISC-V: Add ptrace support for vectors")
ed1a8872ff83 ("soc: renesas: Kconfig: Select the required configs for RZ/Five SoC")
f508b0175578 ("cache: Add L2 cache management for Andes AX45MP RISC-V core")
555dd72bc06e ("dt-bindings: cache: andestech,ax45mp-cache: Add DT binding docu dbe46b094026 ("RISC-V: Add ptrace support for vectors")
ed1a8872ff83 ("soc: renesas: Kconfig: Select the required configs for RZ/Five
SoC")
f508b0175578 ("cache: Add L2 cache management for Andes AX45MP RISC-V core")
555dd72bc06e ("dt-bindings: cache: andestech,ax45mp-cache: Add DT binding docu
mentation for L2 cache controller")
30bc090f40f8 ("riscv: mm: dma-noncoherent: nonstandard cache operations support")
f2863f30d1b0 ("riscv: errata: Add Andes alternative ports")
93e0e2419b65 ("riscv: asm: vendorid_list: Add Andes Technology to the vendors list")
eb76e5111881 ("riscv: dma-mapping: switch over to generic implementation")
14be7c16d420 ("riscv: dma-mapping: skip invalidation before bidirectional DMA")
fbfc740ced8f ("riscv: dma-mapping: only invalidate after DMA, not flush")
b6e3f6e009a1 ("RISC-V: alternative: Remove feature_probe_func")
b98673c5b037 ("RISC-V: Probe for unaligned access speed")
26ba042414a3 ("perf: tests: Adapt mmap-basic.c for riscv")
60bd50116484 ("tools: lib: perf: Implement riscv mmap support")
57972127b20e ("Documentation: admin-guide: Add riscv sysctl_perf_user_access")
cc4c07c89aad ("drivers: perf: Implement perf event mmap support in the SBI backend")
50be34282905 ("drivers: perf: Implement perf event mmap support in the legacy backend")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-30 21:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 21:57 Stephen Rothwell [this message]
2023-09-01 16:14 ` linux-next: Signed-off-by missing for commit in the risc-v tree Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 21:03 Stephen Rothwell
2024-10-24 21:14 ` Palmer Dabbelt
2023-11-02 20:55 Stephen Rothwell
2023-11-02 21:02 ` Palmer Dabbelt
2023-01-18 4:10 Stephen Rothwell
2023-01-18 4:16 ` Palmer Dabbelt
2022-10-27 19:30 Stephen Rothwell
2022-10-27 21:47 ` Palmer Dabbelt
2021-10-04 21:09 Stephen Rothwell
2021-10-04 22:29 ` Palmer Dabbelt
2021-08-26 21:12 Stephen Rothwell
2021-04-25 3:01 Stephen Rothwell
2021-04-26 16:07 ` Palmer Dabbelt
2020-11-08 21:18 Stephen Rothwell
2020-07-11 23:35 Stephen Rothwell
2020-06-06 1:14 Stephen Rothwell
2020-03-31 20:52 Stephen Rothwell
2020-01-30 20:17 Stephen Rothwell
2020-02-05 22:09 ` Palmer Dabbelt
2019-05-08 21:47 Stephen Rothwell
2019-05-08 22:15 ` Palmer Dabbelt
2018-08-05 21:37 Stephen Rothwell
2018-08-06 22:49 ` Palmer Dabbelt
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=20230831075730.0dd941dd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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