From: Hemanth Selam <hemanth.selam@gmail.com>
To: ljs@kernel.org
Cc: david@kernel.org, akpm@linux-foundation.org, shuah@kernel.org,
yury.khrustalev@arm.com, kevin.brodsky@arm.com,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests/mm: remove the local PKEY_UNRESTRICTED fallback
Date: Tue, 25 Aug 2026 21:28:02 +0530 [thread overview]
Message-ID: <20260825155802.2804785-1-hemanth.selam@gmail.com> (raw)
In-Reply-To: <ao2nFqGevXIa3l4c@gremlin>
On Tue, Aug 25, 2026 at 03:36:36PM +0100, Lorenzo Stoakes (ARM) wrote:
> Since you said load-bearing in the last email - I do have to ask if AI was
> involved with this.
>
> If so please adhere to kernel guidelines:
>
> https://docs.kernel.org/process/coding-assistants.html
> https://docs.kernel.org/process/generated-content.html
>
> I.e. add an Assisted-by tag.
Yes, it was. I used an AI assistant while tracing the include path and
preparing the patch. The builds and the cpp output I quoted are ones I ran
and checked myself, and the Signed-off-by is mine, but I should have tagged
the assistance from the start. Sorry for that, and thanks for asking
directly.
The respin will carry
Assisted-by: Cursor:claude-opus-5
I will send it as a new mail rather than in reply to this thread, as you
and David asked.
Thanks for the Acked-by.
Hemanth
prev parent reply other threads:[~2026-08-25 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 11:49 [PATCH] selftests/mm: remove the local PKEY_UNRESTRICTED fallback Hemanth Selam
2026-08-18 13:11 ` David Hildenbrand (Arm)
2026-08-18 13:29 ` Lorenzo Stoakes (ARM)
2026-08-18 14:18 ` David Hildenbrand (Arm)
2026-08-18 14:36 ` Lorenzo Stoakes (ARM)
2026-08-19 7:47 ` Hemanth Selam
2026-08-25 14:30 ` Lorenzo Stoakes (ARM)
2026-08-19 7:47 ` [PATCH v2] " Hemanth Selam
2026-08-19 14:15 ` David Hildenbrand (Arm)
2026-08-25 14:36 ` Lorenzo Stoakes (ARM)
2026-08-25 15:58 ` Hemanth Selam [this message]
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=20260825155802.2804785-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=yury.khrustalev@arm.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