From: Bart Van Assche <bvanassche@acm.org>
To: 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 09:54:08 -0800 [thread overview]
Message-ID: <1548870848.213038.3.camel@acm.org> (raw)
In-Reply-To: <812e9e1426555808ad1bd5fbfda320c6684abc81.1548869844.git.jpinto@synopsys.com>
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:
$ 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?
Thanks,
Bart.
next prev parent reply other threads:[~2019-01-30 17:54 UTC|newest]
Thread overview: 7+ 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 [this message]
2019-01-30 19:15 ` Joao Pinto
2019-01-30 19:15 ` Joao Pinto
2019-02-05 3:37 ` Martin K. Petersen
2019-02-05 14:02 ` Joao Pinto
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=1548870848.213038.3.camel@acm.org \
--to=bvanassche@acm.org \
--cc=Alex.Lemberg@wdc.com \
--cc=joao.pinto@synopsys.com \
--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 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.