linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Christian Brauner <brauner@kernel.org>
Cc: "Shuah Khan" <skhan@linuxfoundation.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Thomas Weißschuh" <thomas@t-8ch.de>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the nolibc tree
Date: Tue, 22 Aug 2023 11:50:12 +0200	[thread overview]
Message-ID: <ZOSE1GoBrrqvBc0i@1wt.eu> (raw)
In-Reply-To: <20230821-raven-abreibung-cc4abe44c9f5@brauner>

Hi,

On Mon, Aug 21, 2023 at 06:07:45PM +0200, Christian Brauner wrote:
> > We will go to our plan b of having Willy drop the patch, resend the
> > pull request to me ....
> 
> No, I didn't drop it so I appreciate it if you went with your plan.
> If I drop it now I'd be causing churn after having this sit in -next for
> over 5 weeks and I'll send a pr in the middle of this week.

I personally don't care about dropping it, but the whole process is
unclear to me and I'm unsure about what I can/have to do if at all
to help here.

Thanks,
Willy

  reply	other threads:[~2023-08-22  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  3:38 linux-next: duplicate patch in the nolibc tree Stephen Rothwell
2023-08-17 16:30 ` Thomas Weißschuh
2023-08-17 18:27   ` Shuah Khan
2023-08-17 18:46     ` Paul E. McKenney
2023-08-17 19:39       ` Willy Tarreau
2023-08-17 20:41         ` Paul E. McKenney
2023-08-18 13:27           ` Christian Brauner
2023-08-18 13:59             ` Shuah Khan
2023-08-21 15:52               ` Shuah Khan
2023-08-21 16:07                 ` Christian Brauner
2023-08-22  9:50                   ` Willy Tarreau [this message]
2023-08-17 19:34     ` Thomas Weißschuh

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=ZOSE1GoBrrqvBc0i@1wt.eu \
    --to=w@1wt.eu \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=skhan@linuxfoundation.org \
    --cc=thomas@t-8ch.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;
as well as URLs for NNTP newsgroup(s).