mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>, "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	linux-kernel@vger.kernel.org,
	"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: nolibc: add myself as co-maintainer
Date: Thu, 3 Aug 2023 14:08:44 -0600	[thread overview]
Message-ID: <29ba0002-0c2f-ff5c-bbf3-fca167f77b3d@linuxfoundation.org> (raw)
In-Reply-To: <20230803191533.GA25279@1wt.eu>

On 8/3/23 13:15, Willy Tarreau wrote:
> On Thu, Aug 03, 2023 at 11:43:17AM -0700, Paul E. McKenney wrote:
>> On Thu, Aug 03, 2023 at 08:31:50PM +0200, Thomas Weißschuh wrote:
>>> Hi Paul,
>>>
>>> On 2023-07-28 23:21:52+0200, Thomas Weißschuh wrote:
>>>> As discussed with Willy, Paul and Shuah add myself as maintainer for
>>>> the nolibc subsystem.
>>>
>>> it seems I forgot to send the nolibc maintainers update patch to you.
>>>
>>> My bad!
>>>
>>> Willy and me wondered if the patch could go through your tree?
>>
>> It could, but why not just include it in the batch going to Shuah?
>> It is not all that long until the merge window opens, plus it is hard
>> to argue that this is a regression.
> 
> OK, I'll take it in my queue and send everything at once to Shuah.
> Thomas and I didn't know if the file had to be updated quickly or
> not.
> 

Sound like a plan.

thanks,
-- Shuah


      reply	other threads:[~2023-08-03 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 21:21 Thomas Weißschuh
2023-07-29  6:53 ` Willy Tarreau
2023-08-03 18:31 ` Thomas Weißschuh
2023-08-03 18:43   ` Paul E. McKenney
2023-08-03 19:15     ` Willy Tarreau
2023-08-03 20:08       ` Shuah Khan [this message]

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=29ba0002-0c2f-ff5c-bbf3-fca167f77b3d@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=paulmck@kernel.org \
    --cc=w@1wt.eu \
    /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®