Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Pratyush Yadav <pratyush@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:59:25 +0100	[thread overview]
Message-ID: <akJB9EYPerO90rEh@lucifer> (raw)
In-Reply-To: <4b12ba64-5e2f-492b-80dd-b9be95604026@kernel.org>

On Mon, Jun 29, 2026 at 11:45:03AM +0200, David Hildenbrand (Arm) wrote:
> On 6/29/26 11:37, Lorenzo Stoakes wrote:
> > On Mon, Jun 29, 2026 at 11:25:52AM +0200, Pratyush Yadav wrote:
> >> On Mon, Jun 29 2026, David Hildenbrand (Arm) wrote:
> >>
> >>>
> >>> [...]
> >>>
> >>>
> >>> 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.
>
> Yes, I saw it on bigger stuff as well, but not on small stuff, really.
>
> >>
> >> 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.
>
> Guess it gets interesting once the SOB does not carry that information. Also,
> some people might work at company X (and send code from company mail address)
> but may hold all copyright by themselves.
>
> So even the git log cannot tell that story.
>
> But in any case, I would expect a comment about that in the patch description :)

Right yeah that'd be nice agreed :)

>
> --
> Cheers,
>
> David

Cheers, Lorenzo


  reply	other threads:[~2026-06-29  9:59 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
2026-06-29  9:45       ` David Hildenbrand (Arm)
2026-06-29  9:59         ` Lorenzo Stoakes [this message]
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=akJB9EYPerO90rEh@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