From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] MAINTAINERS: at91: remove the TC entry
Date: Fri, 23 Aug 2019 21:51:33 +0200 [thread overview]
Message-ID: <20190823195133.GF30479@piout.net> (raw)
In-Reply-To: <20190823083158.2649-2-nicolas.ferre@microchip.com>
On 23/08/2019 10:31:57+0200, Nicolas Ferre wrote:
> "MICROCHIP TIMER COUNTER (TC) AND CLOCKSOURCE DRIVERS" is better
> removed because one file entry is outdated and basically, the
> maintainer's pool of Alexandre, Ludovic and myself is better suited.
>
> drivers/misc/atmel_tclib.c file is going away in a patch to come and
> drivers/clocksource/tcb_clksrc.c file is actually named timer-atmel-tcb.c.
> This new name is catches by AT91 entry regular expression.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> MAINTAINERS | 7 -------
> 1 file changed, 7 deletions(-)
>
Applied, thanks.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-23 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 8:31 [PATCH 1/3] MAINTAINERS: at91: Collect all pinctrl/gpio drivers in same entry Nicolas Ferre
2019-08-23 8:31 ` [PATCH 2/3] MAINTAINERS: at91: remove the TC entry Nicolas Ferre
2019-08-23 19:51 ` Alexandre Belloni [this message]
2019-08-23 8:31 ` [PATCH 3/3] mailmap: map old company name to new one @microchip.com Nicolas Ferre
2019-08-23 19:51 ` Alexandre Belloni
2019-08-23 19:51 ` [PATCH 1/3] MAINTAINERS: at91: Collect all pinctrl/gpio drivers in same entry Alexandre Belloni
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=20190823195133.GF30479@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@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).