From: Lorenzo Stoakes <ljs@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: s/SeongJae/SJ/
Date: Mon, 29 Jun 2026 10:37:41 +0100 [thread overview]
Message-ID: <akI8lkVb5CICUcWi@lucifer> (raw)
In-Reply-To: <2vxzo6gtk89r.fsf@kernel.org>
On Mon, Jun 29, 2026 at 11:25:52AM +0200, Pratyush Yadav wrote:
> On Mon, Jun 29 2026, David Hildenbrand (Arm) wrote:
>
> > On 6/27/26 21:56, SJ Park wrote:
> >> My legal name and preferred first names are SeongJae and SJ,
> >> respectively. I was using the legal name for commits and tags, while
> >> using the preferred name for conversations. It sometimes confuses
> >> people including myself. Consistently use the preferred name.
> >>
> >> Signed-off-by: SJ Park <sj@kernel.org>
> >
> > [...]
> >
> >> #include <linux/pid.h>
> >> diff --git a/mm/damon/tests/core-kunit.h b/mm/damon/tests/core-kunit.h
> >> index 1cfb8c176b873..fcf7c7fadb5fe 100644
> >> --- a/mm/damon/tests/core-kunit.h
> >> +++ b/mm/damon/tests/core-kunit.h
> >> @@ -1,10 +1,6 @@
> >> /* SPDX-License-Identifier: GPL-2.0 */
> >> /*
> >> * Data Access Monitor Unit Tests
> >> - *
> >> - * Copyright 2019 Amazon.com, Inc. or its affiliates. All rights reserved.
> >> - *
> >> - * Author: SeongJae Park <sj@kernel.org>
> >
> > Just curious, why do you drop the author and copyright information? (can you
> > even drop the Amazon copyright note?)
>
> Off topic, but I am curious how these copyright notices are supposed to
> work in the first place. From what I have seen, the person who creates
> the file normally adds one for themselves/their employer. But then other
> contributors who make small/medium changes don't add theirs, even though
> they should hold the copyright for the code they added. Bigger refactors
> sometimes add a notice but that isn't done consistently either.
>
> So do these notices even hold any value? They certainly don't list all
> the entities who hold the copyright to the code in the file. Only git
> log can tell you that. Is there even any point in adding them?
It strikes me as a rather loose convention.
I am not a lawyer, but I would say that individual and corporate ownership of
code are implied by S-o-b, not by comments in files.
Certainly there's not been consistency on this!
>
> [...]
>
> --
> Regards,
> Pratyush Yadav
Thanks, Lorenzo
next prev parent reply other threads:[~2026-06-29 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 19:56 [PATCH] MAINTAINERS: s/SeongJae/SJ/ SJ Park
2026-06-27 20:00 ` SJ Park
2026-06-29 6:30 ` David Hildenbrand (Arm)
2026-06-29 9:25 ` Pratyush Yadav
2026-06-29 9:37 ` Lorenzo Stoakes [this message]
2026-06-29 9:45 ` David Hildenbrand (Arm)
2026-06-29 9:59 ` Lorenzo Stoakes
2026-06-29 13:23 ` SJ Park
2026-06-29 9:38 ` Lorenzo Stoakes
2026-06-29 13:24 ` SJ Park
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=akI8lkVb5CICUcWi@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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