linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the mtd tree with the vfs-brauner tree
Date: Tue, 31 Oct 2023 15:50:13 +0100 (CET)	[thread overview]
Message-ID: <111052022.28286.1698763813964.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20231031154631.61e5f83e@xps-13>

----- Ursprüngliche Mail -----
> Von: "Miquel Raynal" <miquel.raynal@bootlin.com>
>> vfs-6.7.super was merged yesterday, if that's what this is about.
> 
> Great, thanks for the confirmation. Then Richard you have your upstream
> commit already!

Well, I'd like to back port ff6abbe85634, which is not upstream.
But I'll try to argue that ff6abbe85634 is the super simple variant of 1bcded92d938.

Thanks,
//richard

  reply	other threads:[~2023-10-31 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 23:34 linux-next: manual merge of the mtd tree with the vfs-brauner tree Stephen Rothwell
2023-10-30 16:32 ` Miquel Raynal
2023-10-30 20:11   ` Richard Weinberger
2023-10-31  8:51     ` Jan Kara
2023-10-31  9:02       ` Richard Weinberger
2023-10-31 10:33         ` Christian Brauner
2023-10-31 11:30           ` Richard Weinberger
2023-10-31 12:45             ` Miquel Raynal
2023-10-31 13:13               ` Richard Weinberger
2023-10-31 13:50                 ` Miquel Raynal
2023-10-31 14:25                   ` Christian Brauner
2023-10-31 14:46                     ` Miquel Raynal
2023-10-31 14:50                       ` Richard Weinberger [this message]
2023-10-31 12:29         ` Jan Kara

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=111052022.28286.1698763813964.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard.weinberger@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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).