linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christian Brauner <brauner@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the block tree
Date: Tue, 12 Dec 2023 08:01:38 -0700	[thread overview]
Message-ID: <b203a609-1f5e-4d1f-861b-c252ea164c99@kernel.dk> (raw)
In-Reply-To: <20231212-innung-zuber-2f10bcffac51@brauner>

On 12/12/23 6:38 AM, Christian Brauner wrote:
> On Tue, Dec 12, 2023 at 01:02:13PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commits are also in the vfs-brauner tree as different
>> commits (but the same patches):
> 
> Thanks, Stephen. I gave Jens a stable vfs.file branch that he can pull
> into his so this shouldn't become an issue again.

Should be clean now, rebased with the stable branch pulled in first.

-- 
Jens Axboe



  reply	other threads:[~2023-12-12 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  2:02 linux-next: duplicate patches in the block tree Stephen Rothwell
2023-12-12 13:38 ` Christian Brauner
2023-12-12 15:01   ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-21  2:56 Stephen Rothwell
2023-12-21  3:11 ` Jens Axboe
2023-12-21 12:29   ` Christian Brauner
2023-12-21 15:32     ` Jens Axboe
2023-08-07  4:51 Stephen Rothwell
2023-08-07 18:16 ` Jens Axboe
2023-02-20  1:02 Stephen Rothwell
2023-02-20  1:47 ` David Howells
2023-02-20  2:49   ` Stephen Rothwell

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=b203a609-1f5e-4d1f-861b-c252ea164c99@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).