All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: SJ Park <sj@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	 Lorenzo Stoakes <ljs@kernel.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 11:25:52 +0200	[thread overview]
Message-ID: <2vxzo6gtk89r.fsf@kernel.org> (raw)
In-Reply-To: <e29d1211-8bc3-433a-b1d7-d7fb44c2f0cd@kernel.org> (David Hildenbrand's message of "Mon, 29 Jun 2026 08:30:23 +0200")

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?

[...]

-- 
Regards,
Pratyush Yadav


  reply	other threads:[~2026-06-29  9:26 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 ` sashiko-bot
2026-06-27 20:46   ` SJ Park
2026-06-27 20:00 ` SJ Park
2026-06-29  6:30 ` David Hildenbrand (Arm)
2026-06-29  9:25   ` Pratyush Yadav [this message]
2026-06-29  9:37     ` Lorenzo Stoakes
2026-06-29  9:45       ` David Hildenbrand (Arm)
2026-06-29  9:59         ` Lorenzo Stoakes
2026-06-29  9:38 ` Lorenzo Stoakes

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=2vxzo6gtk89r.fsf@kernel.org \
    --to=pratyush@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=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --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 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.