From: Boris Brezillon <bbrezillon@kernel.org>
To: <Tudor.Ambarus@microchip.com>
Cc: <marek.vasut@gmail.com>, <boris.brezillon@bootlin.co>,
<richard@nod.at>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <miquel.raynal@bootlin.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add myself as SPI NOR co-maintainer
Date: Tue, 15 Jan 2019 18:10:55 +0100 [thread overview]
Message-ID: <20190115181038.2a670a4e@bbrezillon> (raw)
In-Reply-To: <20190115165740.32450-1-tudor.ambarus@microchip.com>
Hi Tudor,
On Tue, 15 Jan 2019 16:57:52 +0000
<Tudor.Ambarus@microchip.com> wrote:
> From: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> I have been reviewing and contributing to the SPI NOR subsystem
> for the last few months and I'm willing to continue doing so.
> Volunteer as a maintainer for the SPI NOR part of the MTD subsystem.
I'll wait a bit before applying this patch to let other maintainers ack
or nack it if they want, but I must say that's a huge relief for me to
have a new person handling SPI NOR patches on board.
Thanks a lot for doing that.
Regards,
Boris
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6682420421c1..7deb0e91e3ed 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14081,6 +14081,7 @@ F: arch/arm/mach-spear/
>
> SPI NOR SUBSYSTEM
> M: Marek Vasut <marek.vasut@gmail.com>
> +M: Tudor Ambarus <tudor.ambarus@microchip.com>
> L: linux-mtd@lists.infradead.org
> W: http://www.linux-mtd.infradead.org/
> Q: http://patchwork.ozlabs.org/project/linux-mtd/list/
next prev parent reply other threads:[~2019-01-15 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 16:57 [PATCH] MAINTAINERS: add myself as SPI NOR co-maintainer Tudor.Ambarus
2019-01-15 17:10 ` Boris Brezillon [this message]
2019-01-15 17:53 ` Miquel Raynal
2019-01-15 17:54 ` Marek Vasut
2019-01-15 18:15 ` Richard Weinberger
2019-01-16 12:57 ` Boris Brezillon
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=20190115181038.2a670a4e@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=Tudor.Ambarus@microchip.com \
--cc=boris.brezillon@bootlin.co \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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).