public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <joao.pinto@synopsys.com>
To: Bart Van Assche <bvanassche@acm.org>,
	Joao Pinto <joao.pinto@synopsys.com>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <pedrom.sousa@synopsys.com>, <marc.w.gonzalez@free.fr>,
	<Alex.Lemberg@wdc.com>
Subject: Re: [PATCH for-next] scsi: ufs: Update dwc driver maintainer to Pedro Sousa
Date: Wed, 30 Jan 2019 19:15:56 +0000	[thread overview]
Message-ID: <f0ff398e-cc13-d70d-0488-d35faa126a5a@synopsys.com> (raw)
In-Reply-To: <1548870848.213038.3.camel@acm.org>

Hello Bart,

First of all thanks for the feedback.

On 1/30/2019 5:54 PM, Bart Van Assche wrote:
> On Wed, 2019-01-30 at 18:48 +0100, Joao Pinto wrote:
>> Currently I am managing the Synopsys drivers & tools team (full-time) and
>> so I am passing the DWC UFS driver maintenance to Pedro Sousa.
>>
>> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
>> Cc: Pedro Sousa <pedrom.sousa@synopsys.com>
>> Cc: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> Cc: Alex Lemberg <Alex.Lemberg@wdc.com>
>> ---
>>  MAINTAINERS | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 70c93b1..458a2a2 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -15673,7 +15673,7 @@ F:	Documentation/scsi/ufs.txt
>>  F:	drivers/scsi/ufs/
>>  
>>  UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER DWC HOOKS
>> -M:	Joao Pinto <jpinto@synopsys.com>
>> +M:	Pedro Sousa <pedrom.sousa@synopsys.com>
>>  L:	linux-scsi@vger.kernel.org
>>  S:	Supported
>>  F:	drivers/scsi/ufs/*dwc*
> Shouldn't people have proven to be willing to stick around before being
> added as a kernel maintainer? Additionally, what is the experience level of
> Pedro with kernel development? All I know is the following:

Pedro Sousa is my team member and has been working in Unipro/UFS Synopsys
drivers for almost 2 years.

His work has been mainly internal, and now our goal is to start using the
mainline DWC UFS driver I submitted 2 years ago in our regular activities,
update and maintain it effectively as we are doing in other titles.

Currently I am Pedro' manager, and in my opinion he has the right experience for
this step and that is why I am suggesting to transfer Synopsys driver
maintenance from me to him.

>
> $ git log --author "Pedro Sousa" | wc -l
> 0
> $ git log | grep -c "Pedro Sousa"
> 0
>
> Are you aware that people who are not mentioned in the MAINTAINERS file are
> allowed to review kernel patches?

Yes, I am aware and Pedro is perfectly capable of doing that, and for that
reason I am suggesting him as the right person to maintain Synopsys UFS driver.

>
> Thanks,
>
> Bart.
>
Thanks,

Joao



  reply	other threads:[~2019-01-30 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 17:48 [PATCH for-next] scsi: ufs: Update dwc driver maintainer to Pedro Sousa Joao Pinto
2019-01-30 17:54 ` Bart Van Assche
2019-01-30 19:15   ` Joao Pinto [this message]
2019-02-05  3:37 ` Martin K. Petersen
2019-02-05 14:02   ` Joao Pinto

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=f0ff398e-cc13-d70d-0488-d35faa126a5a@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=Alex.Lemberg@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=pedrom.sousa@synopsys.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