From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Ingo Molnar <mingo@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <linux-tip-commits@vger.kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Charlie Jenkins <thecharlesjenkins@gmail.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>, <x86@kernel.org>
Subject: Re: [tip: locking/core] riscv/runtime-const: Introduce runtime_const_mask_32()
Date: Wed, 29 Jul 2026 15:59:51 +0530 [thread overview]
Message-ID: <bfa9014e-f1ca-479e-bd3d-ca284f45e71f@amd.com> (raw)
In-Reply-To: <amnQBmyFniPpIZ7Q@gmail.com>
Hello Ingo, Peter,
On 7/29/2026 3:33 PM, Ingo Molnar wrote:
>
> * tip-bot2 for K Prateek Nayak <tip-bot2@linutronix.de> wrote:
>
>> The following commit has been merged into the locking/core branch of tip:
>>
>> Commit-ID: 3f0d06613ae58ae09c48915638692d093168abc1
>> Gitweb: https://git.kernel.org/tip/3f0d06613ae58ae09c48915638692d093168abc1
>> Author: K Prateek Nayak <kprateek.nayak@amd.com>
>> AuthorDate: Tue, 28 Jul 2026 05:25:37
>> Committer: Peter Zijlstra <peterz@infradead.org>
>> CommitterDate: Tue, 28 Jul 2026 13:07:15 +02:00
>>
>> riscv/runtime-const: Introduce runtime_const_mask_32()
>
>> Suggested-by: Samuel Holland <samuel.holland@sifive.com>
>> Suggested-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
>> Assisted-by: Claude:claude-sonnet-4-5
>> Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
>> Signed-off-by: K Prateek Nayak <kprateek.nayak@amd.com>
>> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> So author is Prateek, but the first SOB is Chalie Jenkins's?
> That's not a valid SOB chain.
>
> Is a 'From: Charlie' line missing, or was it Co-developed-by?
That was b4 picking up a S-o-b for a parallel suggestion here
https://lore.kernel.org/lkml/alXQY4hgZYLmr8x7@blinky/
Sorry I didn't catch this earlier. Could you please drop that tag.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-07-29 10:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 5:25 [PATCH v6 0/8] futex: Use runtime constants for futex_hash computation K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 1/8] x86/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-07-28 5:25 ` [PATCH v6 2/8] arm64/runtime-const: Use aarch64_insn_patch_text_nosync() for patching K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 3/8] arm64/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 4/8] riscv/runtime-const: Replace open-coded placeholder with RUNTIME_MAGIC K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 5/8] riscv/runtime-const: Introduce runtime_const_mask_32() K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for K Prateek Nayak
2026-07-29 10:03 ` Ingo Molnar
2026-07-29 10:29 ` K Prateek Nayak [this message]
2026-07-29 11:21 ` Peter Zijlstra
2026-07-29 11:22 ` tip-bot2 for K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 6/8] s390/runtime-const: " K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for K Prateek Nayak
2026-07-29 11:22 ` tip-bot2 for K Prateek Nayak
2026-07-28 5:25 ` [PATCH v6 7/8] asm-generic/runtime-const: Add dummy runtime_const_mask_32() K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-07-29 11:22 ` tip-bot2 for Peter Zijlstra
2026-07-28 5:25 ` [PATCH v6 8/8] futex: Use runtime constants for __futex_hash() hot path K Prateek Nayak
2026-07-28 10:46 ` Peter Zijlstra
2026-07-28 11:08 ` Peter Zijlstra
2026-07-29 6:49 ` K Prateek Nayak
2026-07-29 9:55 ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-07-29 11:22 ` tip-bot2 for Peter Zijlstra
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=bfa9014e-f1ca-479e-bd3d-ca284f45e71f@amd.com \
--to=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=samuel.holland@sifive.com \
--cc=thecharlesjenkins@gmail.com \
--cc=x86@kernel.org \
/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