public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Sagar Biradar <sagar.biradar@microchip.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jack Wang <jinpu.wang@cloud.ionos.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	stable@vger.kernel.org, Don Brace <don.brace@microchip.com>,
	Raja VS <raja.vs@microchip.com>,
	Kumar Meiyappan <kumar.meiyappan@microchip.com>,
	Abhinav Kuchibhotla <abhinav.kuchibhotla@microchip.com>,
	Uday kumar Bagam <udaykumar.bagam@microchip.com>,
	Advait Churi <advait.churi@microchip.com>
Subject: Re: [PATCH] scsi: pm8001: add MODULE_AUTHOR entries for new contributors
Date: Fri, 24 Apr 2026 11:35:20 +0900	[thread overview]
Message-ID: <66414927-481a-4464-8a3d-d6d77ab1aefb@kernel.org> (raw)
In-Reply-To: <20260421212218.433963-1-sagar.biradar@microchip.com>

On 4/22/26 06:22, Sagar Biradar wrote:
> Add MODULE_AUTHOR declarations for the developers who have
> been actively working on the pm8001/pm80xx driver in recent years.
> 
> This helps properly credit the people involved in the ongoing
> maintenance and the current upstreaming effort.
> 
> Signed-off-by: Sagar Biradar <sagar.biradar@microchip.com>

Well, if you go there, then you are really missing *a lot* of people.
Just run:

git shortlog -n -s -- drivers/scsi/pm8001

and see the ranking by number of commits.

So in the end, I really do not see the point of this patch since git log can
give a full (and correct) list of contributors.

> ---
>  drivers/scsi/pm8001/pm8001_init.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/scsi/pm8001/pm8001_init.c b/drivers/scsi/pm8001/pm8001_init.c
> index e93ea76b565e..487f9bc237ef 100644
> --- a/drivers/scsi/pm8001/pm8001_init.c
> +++ b/drivers/scsi/pm8001/pm8001_init.c
> @@ -1569,6 +1569,9 @@ MODULE_AUTHOR("Jack Wang <jack_wang@usish.com>");
>  MODULE_AUTHOR("Anand Kumar Santhanam <AnandKumar.Santhanam@pmcs.com>");
>  MODULE_AUTHOR("Sangeetha Gnanasekaran <Sangeetha.Gnanasekaran@pmcs.com>");
>  MODULE_AUTHOR("Nikith Ganigarakoppal <Nikith.Ganigarakoppal@pmcs.com>");
> +MODULE_AUTHOR("Abhinav Kuchibhotla <Abhinav.Kuchibhotla@microchip.com>");
> +MODULE_AUTHOR("Kumar Meiyappan <Kumar.Meiyappan@microchip.com>");
> +MODULE_AUTHOR("Sagar Biradar <Sagar.Biradar@microchip.com>");
>  MODULE_DESCRIPTION(
>  		"PMC-Sierra PM8001/8006/8081/8088/8089/8074/8076/8077/8070/8072 "
>  		"SAS/SATA controller driver");


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2026-04-24  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 21:22 [PATCH] scsi: pm8001: add MODULE_AUTHOR entries for new contributors Sagar Biradar
2026-04-24  2:35 ` Damien Le Moal [this message]
2026-04-24  6:00   ` Jinpu Wang
2026-04-24 20:46     ` Sagar.Biradar

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=66414927-481a-4464-8a3d-d6d77ab1aefb@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=abhinav.kuchibhotla@microchip.com \
    --cc=advait.churi@microchip.com \
    --cc=don.brace@microchip.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=kumar.meiyappan@microchip.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=raja.vs@microchip.com \
    --cc=sagar.biradar@microchip.com \
    --cc=stable@vger.kernel.org \
    --cc=udaykumar.bagam@microchip.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