mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Shuah Khan <skhan@linuxfoundation.org>, Willy Tarreau <w@1wt.eu>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Zhangjin Wu <falcon@tinylab.org>
Subject: Re: linux-next: manual merge of the nolibc tree with the vfs-brauner tree
Date: Thu, 24 Aug 2023 10:33:40 +0200	[thread overview]
Message-ID: <26bc62c7-32c7-4ef1-b8d1-77738fa98598@t-8ch.de> (raw)
In-Reply-To: <20230824-moment-wehten-5a47e319ae66@brauner>

On 2023-08-24 09:36:58+0200, Christian Brauner wrote:
> > You mentioned before that you plan to have this series in
> > -next for some time. If you only submit it to Linux for 6.7 or later
> 
> I'm not sure what this is about. v6.6 was always the plan.

I'm referring to "In any case, this needs long soaking in -next." [0]

Which I interpreted as "longer than usual", where "usual" would have
been v6.6.

Anyways Linus should also be able to resolve the conflict for v6.6 with
a small hint in the PR.

[0] https://lore.kernel.org/lkml/20230713-schwalben-anproben-6af2eac149fd@brauner/

  reply	other threads:[~2023-08-24  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  4:10 Stephen Rothwell
2023-08-24  6:27 ` Thomas Weißschuh
2023-08-24  6:40   ` Willy Tarreau
2023-08-24  7:36   ` Christian Brauner
2023-08-24  8:33     ` Thomas Weißschuh [this message]
2023-08-24  8:52       ` Christian Brauner
2023-08-24 14:24         ` Shuah Khan

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=26bc62c7-32c7-4ef1-b8d1-77738fa98598@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=brauner@kernel.org \
    --cc=falcon@tinylab.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=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®