From: Mark Brown <broonie@kernel.org>
To: nicolas.ferre@microchip.com
Cc: linux-arm-kernel@lists.infradead.org, sre@kernel.org,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-spi@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: Change Maintainer for some at91 drivers
Date: Thu, 2 Jul 2020 15:39:09 +0100 [thread overview]
Message-ID: <20200702143909.GH4483@sirena.org.uk> (raw)
In-Reply-To: <20200702134224.3750-1-nicolas.ferre@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
On Thu, Jul 02, 2020 at 03:42:24PM +0200, nicolas.ferre@microchip.com wrote:
> I kept these entries together as it may generate conflicts if handled
> separately. I suggest that Mark take the chunk as maintainer of SPI and
> Audio sub-systems.
> Anyway, don't hesitate to tell me if I should handle this change
> differently or at another time during the development cycle.
That works for me (though I'd be a bit surprised if it generated
conflicts), Sebastian?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-02 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 13:42 [PATCH] MAINTAINERS: Change Maintainer for some at91 drivers nicolas.ferre
2020-07-02 14:39 ` Mark Brown [this message]
2020-07-02 16:11 ` Sebastian Reichel
2020-07-03 17:03 ` Mark Brown
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=20200702143909.GH4483@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=sre@kernel.org \
--cc=tudor.ambarus@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;
as well as URLs for NNTP newsgroup(s).