All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <thecharlesjenkins@gmail.com>
Cc: linux-riscv@lists.infradead.org, shuah@kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, geomatsi@gmail.com,
	andybnac@gmail.com, debug@rivosinc.com,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi
Date: Fri, 03 Apr 2026 18:30:04 +0000	[thread overview]
Message-ID: <177524100454.1406513.15002331983137680726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309-fix_selftests-v2-0-9d5a553a531e@gmail.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 09 Mar 2026 18:52:09 -0700 you wrote:
> There are a couple of compilation issues of the riscv selftests.
> Coincidentally two of the issues are independent problems with not
> including the header that includes the BIT() macro and the other issue
> is from checkpatch incorrectly suggesting to remove non-redundant
> braces.
> 
> Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
> 
> [...]

Here is the summary with links:
  - [v2,1/4] selftests: riscv: Add definition of BIT() macro
    (no matching commit)
  - [v2,2/4] selftests: riscv: Add braces around EXPECT_EQ()
    https://git.kernel.org/riscv/c/2ff48e038210
  - [v2,3/4] riscv: ptrace: Fix BIT() compilation issues
    (no matching commit)
  - [v2,4/4] selftests: riscv: Add license to cfi selftest
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <thecharlesjenkins@gmail.com>
Cc: linux-riscv@lists.infradead.org, shuah@kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, geomatsi@gmail.com,
	andybnac@gmail.com, debug@rivosinc.com,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi
Date: Fri, 03 Apr 2026 18:30:04 +0000	[thread overview]
Message-ID: <177524100454.1406513.15002331983137680726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309-fix_selftests-v2-0-9d5a553a531e@gmail.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:

On Mon, 09 Mar 2026 18:52:09 -0700 you wrote:
> There are a couple of compilation issues of the riscv selftests.
> Coincidentally two of the issues are independent problems with not
> including the header that includes the BIT() macro and the other issue
> is from checkpatch incorrectly suggesting to remove non-redundant
> braces.
> 
> Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
> 
> [...]

Here is the summary with links:
  - [v2,1/4] selftests: riscv: Add definition of BIT() macro
    (no matching commit)
  - [v2,2/4] selftests: riscv: Add braces around EXPECT_EQ()
    https://git.kernel.org/riscv/c/2ff48e038210
  - [v2,3/4] riscv: ptrace: Fix BIT() compilation issues
    (no matching commit)
  - [v2,4/4] selftests: riscv: Add license to cfi selftest
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-04-03 18:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  1:52 [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi Charlie Jenkins
2026-03-10  1:52 ` Charlie Jenkins via B4 Relay
2026-03-10  1:52 ` Charlie Jenkins via B4 Relay
2026-03-10  1:52 ` [PATCH v2 1/4] selftests: riscv: Add definition of BIT() macro Charlie Jenkins
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  8:18   ` Sergey Matyukevich
2026-03-10  8:18     ` Sergey Matyukevich
2026-03-21  0:48     ` Paul Walmsley
2026-03-21  0:48       ` Paul Walmsley
2026-03-21  0:53   ` Paul Walmsley
2026-03-21  0:53     ` Paul Walmsley
2026-03-10  1:52 ` [PATCH v2 2/4] selftests: riscv: Add braces around EXPECT_EQ() Charlie Jenkins
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  3:50   ` Joe Perches
2026-03-10  3:50     ` Joe Perches
2026-03-10  8:17   ` Sergey Matyukevich
2026-03-10  8:17     ` Sergey Matyukevich
2026-03-21  0:24   ` Paul Walmsley
2026-03-21  0:24     ` Paul Walmsley
2026-04-03 17:46     ` Paul Walmsley
2026-04-03 17:46       ` Paul Walmsley
2026-03-10  1:52 ` [PATCH v2 3/4] riscv: ptrace: Fix BIT() compilation issues Charlie Jenkins
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  2:58   ` Deepak Gupta
2026-03-10  2:58     ` Deepak Gupta
2026-03-21  0:53   ` Paul Walmsley
2026-03-21  0:53     ` Paul Walmsley
2026-03-10  1:52 ` [PATCH v2 4/4] selftests: riscv: Add license to cfi selftest Charlie Jenkins
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  1:52   ` Charlie Jenkins via B4 Relay
2026-03-10  2:58   ` Deepak Gupta
2026-03-10  2:58     ` Deepak Gupta
2026-03-21  0:54   ` Paul Walmsley
2026-03-21  0:54     ` Paul Walmsley
2026-03-21  5:20 ` [PATCH v2 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi patchwork-bot+linux-riscv
2026-03-21  5:20   ` patchwork-bot+linux-riscv
2026-04-03 18:30 ` patchwork-bot+linux-riscv [this message]
2026-04-03 18:30   ` patchwork-bot+linux-riscv

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=177524100454.1406513.15002331983137680726.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=andybnac@gmail.com \
    --cc=debug@rivosinc.com \
    --cc=geomatsi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=shuah@kernel.org \
    --cc=thecharlesjenkins@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.