From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: david@redhat.com, surenb@google.com, aarcange@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/userfaultfd: fix kmap_local LIFO ordering for CONFIG_HIGHPTE
Date: Wed, 20 Aug 2025 21:24:23 -0700 [thread overview]
Message-ID: <20250820212423.fbac2b17eb4f6a9667a8c979@linux-foundation.org> (raw)
In-Reply-To: <aI04CQZZzgCDO2A5@lappy>
On Fri, 1 Aug 2025 17:56:25 -0400 Sasha Levin <sashal@kernel.org> wrote:
> >> Fixes: adef440691ba ("userfaultfd: UFFDIO_MOVE uABI")
> >> Co-developed-by: Claude claude-opus-4-20250514
> >
> >Well this is innovative. I doubt if Co-developed-by: is appropriate
> >for this (where's Claude's Signed-off-by:?)
>
> Claude (or any other AI) can't legally sign off on code :)
>
> >I'd support creating a new changelog tag for this case.
>
> This is in the context of a proposal on workflows@:
> https://lore.kernel.org/workflows/20250728105634.GF787@pendragon.ideasonboard.com/T/#t
>
> The Co-developed-by: usage wasn't my proposal, but it looked like the
> majority of folks were okay with it.
>
I need to do something about this and the discussion over on
ksummit@lists.linux.dev has been as beer-addled as one would expect.
Oh well. I guess for now we can welcome Claude to the kernel
development team.
next prev parent reply other threads:[~2025-08-21 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:44 Sasha Levin
2025-08-01 21:11 ` Andrew Morton
2025-08-01 21:56 ` Sasha Levin
2025-08-04 8:09 ` David Hildenbrand
2025-08-21 4:24 ` Andrew Morton [this message]
2025-08-21 13:02 ` Sasha Levin
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=20250820212423.fbac2b17eb4f6a9667a8c979@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sashal@kernel.org \
--cc=surenb@google.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