linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: claudiu.beznea@tuxon.dev, nicolas.ferre@microchip.com,
	dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove T Ambarus from few mchp entries
Date: Mon, 26 Feb 2024 11:21:32 +0100	[thread overview]
Message-ID: <20240226112132.22025454@xps-13> (raw)
In-Reply-To: <20240226094718.29104-1-tudor.ambarus@linaro.org>

Hi Tudor,

tudor.ambarus@linaro.org wrote on Mon, 26 Feb 2024 11:47:18 +0200:

> I have been no longer at Microchip for more than a year and I'm no
> longer interested in maintaining these drivers. Let other mchp people
> step up, thus remove myself. Thanks for the nice collaboration everyone!
> 
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
> Shall be queued through the at91 tree.
> 
>  MAINTAINERS | 14 --------------
>  1 file changed, 14 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e1475ca38ff2..fd4d4e58fead 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14350,7 +14350,6 @@ F:	drivers/misc/xilinx_tmr_manager.c
>  
>  MICROCHIP AT91 DMA DRIVERS
>  M:	Ludovic Desroches <ludovic.desroches@microchip.com>
> -M:	Tudor Ambarus <tudor.ambarus@linaro.org>
>  L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>  L:	dmaengine@vger.kernel.org
>  S:	Supported
> @@ -14398,12 +14397,6 @@ S:	Supported
>  F:	Documentation/devicetree/bindings/media/microchip,csi2dc.yaml
>  F:	drivers/media/platform/microchip/microchip-csi2dc.c
>  
> -MICROCHIP ECC DRIVER
> -M:	Tudor Ambarus <tudor.ambarus@linaro.org>
> -L:	linux-crypto@vger.kernel.org
> -S:	Maintained
> -F:	drivers/crypto/atmel-ecc.*
> -
>  MICROCHIP EIC DRIVER
>  M:	Claudiu Beznea <claudiu.beznea@tuxon.dev>
>  L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> @@ -14505,13 +14498,6 @@ M:	Aubin Constans <aubin.constans@microchip.com>
>  S:	Maintained
>  F:	drivers/mmc/host/atmel-mci.c
>  
> -MICROCHIP NAND DRIVER
> -M:	Tudor Ambarus <tudor.ambarus@linaro.org>
> -L:	linux-mtd@lists.infradead.org
> -S:	Supported
> -F:	Documentation/devicetree/bindings/mtd/atmel-nand.txt
> -F:	drivers/mtd/nand/raw/atmel/*

Could we mark these entries orphaned instead of removing them?

> -
>  MICROCHIP OTPC DRIVER
>  M:	Claudiu Beznea <claudiu.beznea@tuxon.dev>
>  L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)


Thanks,
Miquèl

  reply	other threads:[~2024-02-26 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  9:47 [PATCH] MAINTAINERS: Remove T Ambarus from few mchp entries Tudor Ambarus
2024-02-26 10:21 ` Miquel Raynal [this message]
2024-02-26 11:45   ` Tudor Ambarus

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=20240226112132.22025454@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=tudor.ambarus@linaro.org \
    /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).