public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	linux-mips@vger.kernel.org, john@phrozen.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add myself as maintainer of the Ralink architecture
Date: Tue, 5 Dec 2023 21:44:50 +0100	[thread overview]
Message-ID: <ZW+LwrhW9m/vrmnN@alpha.franken.de> (raw)
In-Reply-To: <CAMhs-H_ojHprCxsRwfXo_xavSYv9YH0eppg9ZobscvQamcDNxg@mail.gmail.com>

On Tue, Dec 05, 2023 at 08:58:29PM +0100, Sergio Paracuellos wrote:
> On Tue, Nov 21, 2023 at 1:43 PM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
> >
> > On Tue, Nov 21, 2023 at 10:02 AM Thomas Bogendoerfer
> > <tsbogend@alpha.franken.de> wrote:
> > >
> > > On Mon, Nov 20, 2023 at 08:59:25PM +0100, Sergio Paracuellos wrote:
> > > > On Wed, Oct 25, 2023 at 2:58 PM Philippe Mathieu-Daudé
> > > > <philmd@linaro.org> wrote:
> > > > >
> > > > > 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>
> > > > > > ---
> > > > > > 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(+)
> > > > >
> > > > > Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> > > > >
> > > >
> > > > Thomas, can you take this patch through the mips tree?
> > >
> > > sure
> >
> > Thanks!
> 
> Gentle ping for this patch :)

I've not forgotten it

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-12-05 22:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22  9:06 [PATCH] MAINTAINERS: Add myself as maintainer of the Ralink architecture Sergio Paracuellos
2023-10-22 14:33 ` John Crispin
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 [this message]
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=ZW+LwrhW9m/vrmnN@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=philmd@linaro.org \
    --cc=sergio.paracuellos@gmail.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