linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Robert Richter <rrichter@marvell.com>
Cc: Arnd Bergmann <arnd@arndb.de>, arm soc <arm@kernel.org>,
	Jan Glauber <jglauber@marvell.com>,
	Sunil Kovvuri Goutham <sgoutham@marvell.com>,
	George Cherian <gcherian@marvell.com>,
	Ganapatrao Prabhakerrao Kulkarni <gkulkarni@marvell.com>,
	Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"soc@kernel.org" <soc@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Switch to Marvell addresses
Date: Tue, 19 Nov 2019 13:12:00 -0800	[thread overview]
Message-ID: <1e9719feb8c650ea90dec41850fe9058eef59862.camel@perches.com> (raw)
In-Reply-To: <20191119202328.cqfzf5a4svn23h5a@rric.localdomain>

On Tue, 2019-11-19 at 20:23 +0000, Robert Richter wrote:
> Joe,
> 
> thanks for your review.
> 
> On 19.11.19 11:56:53, Joe Perches wrote:
> > Maybe make that change globally in all the files other
> > than MAINTAINERS as well eventually.
> > 
> > arch/arm64/mm/numa.c:6: * Author: Ganapatrao Kulkarni <gkulkarni@cavium.com>
> > arch/mips/cavium-octeon/octeon-usb.c:551:MODULE_AUTHOR("David Daney <david.daney@cavium.com>");
> > arch/mips/include/asm/octeon/cvmx-coremask.h:6: * Copyright (c) 2016  Cavium Inc. (support@cavium.com).
> 
> [...]
> 
> This is a bit past the scope of this patch.

Yup, completely agree, as it seems I understated with "eventually".

>  I will leave that change to the driver's maintainers.

Fine by me.  btw:  There's also entries for @caviumnetworks.com
so those might change one day too.

> I also think that authorship does not
> change even if the author's email address changed or vanished later. I
> am not sure on the general handling of MODULE_AUTHOR(), should that
> always contain a valid email address? Seems not the case. I don't
> think somebody actually sends an email to the author, it is more to
> better identify the author.

Changelog identifies the author, MODULE_AUTHOR is actually
available via modinfo -a, which shows email if entered,
but that may also be rarely used in practice.



      reply	other threads:[~2019-11-19 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191119165549.14570-1-rrichter@marvell.com>
2019-11-19 16:56 ` [PATCH 1/2] MAINTAINERS: update Cavium ThunderX drivers Robert Richter
2019-11-19 19:16   ` Robert Richter
2019-11-19 16:56 ` [PATCH 1/2] MAINTAINERS: Update " Robert Richter
2019-11-19 17:02   ` Baruch Siach
2019-11-19 18:47     ` Robert Richter
2019-11-19 16:56 ` [PATCH 2/2] MAINTAINERS: Switch to Marvell addresses Robert Richter
2019-11-19 17:14   ` Joe Perches
2019-11-19 18:50     ` Robert Richter
2019-11-19 19:56       ` Joe Perches
2019-11-19 20:23         ` Robert Richter
2019-11-19 21:12           ` Joe Perches [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=1e9719feb8c650ea90dec41850fe9058eef59862.camel@perches.com \
    --to=joe@perches.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=gcherian@marvell.com \
    --cc=gkulkarni@marvell.com \
    --cc=jglauber@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrichter@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=soc@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).