From: John Crispin <john@phrozen.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-mips@vger.kernel.org
Cc: tsbogend@alpha.franken.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add myself as maintainer of the Ralink architecture
Date: Sun, 22 Oct 2023 16:33:03 +0200 [thread overview]
Message-ID: <1d6804f3-a5e2-4840-a4ae-7cd2632b3b64@phrozen.org> (raw)
In-Reply-To: <20231022090633.792831-1-sergio.paracuellos@gmail.com>
On 22.10.23 11:06, Sergio Paracuellos wrote:
> Its been a while since I am making contributions to this architecture.
> Hence add myself as maintainer.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
> ---
> Hi John, if you are not ok with this please let me know. In other case
> please ack this patch. I can add myself as Reviewer if you prefer to
> maintain alone this.
>
> Thanks in advance for your time!
>
> Best regards,
> Sergio Paracuellos
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2894f0777537..406c26a6f5d8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17914,6 +17914,7 @@ F: drivers/media/cec/usb/rainshadow/
>
> RALINK MIPS ARCHITECTURE
> M: John Crispin <john@phrozen.org>
> +M: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> L: linux-mips@vger.kernel.org
> S: Maintained
> F: arch/mips/ralink
next prev parent reply other threads:[~2023-10-22 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 9:06 Sergio Paracuellos
2023-10-22 14:33 ` John Crispin [this message]
2023-10-23 4:50 ` Sergio Paracuellos
2023-10-24 5:33 ` Sergio Paracuellos
2023-10-25 12:58 ` Philippe Mathieu-Daudé
2023-11-20 19:59 ` Sergio Paracuellos
2023-11-21 8:07 ` Thomas Bogendoerfer
2023-11-21 12:43 ` Sergio Paracuellos
2023-12-05 19:58 ` Sergio Paracuellos
2023-12-05 20:44 ` Thomas Bogendoerfer
2023-12-06 8:27 ` Sergio Paracuellos
2023-12-11 20:56 ` Thomas Bogendoerfer
2023-12-12 7:09 ` Sergio Paracuellos
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=1d6804f3-a5e2-4840-a4ae-7cd2632b3b64@phrozen.org \
--to=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®