From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.com>
Cc: torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 5.10
Date: Thu, 15 Oct 2020 11:40:11 +1100 [thread overview]
Message-ID: <20201015114011.1f5f985a@canb.auug.org.au> (raw)
In-Reply-To: <cover.1602519695.git.dsterba@suse.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Hi David,
On Mon, 12 Oct 2020 22:25:02 +0200 David Sterba <dsterba@suse.com> wrote:
>
> Mishaps:
>
> - commit 62cf5391209a ("btrfs: move btrfs_rm_dev_replace_free_srcdev
> outside of all locks") is a rebase leftover after the patch got
> merged to 5.9-rc8 as a466c85edc6f ("btrfs: move
> btrfs_rm_dev_replace_free_srcdev outside of all locks"), the
> remaining part is trivial and the patch is in the middle of the
> series so I'm keeping it there instead of rebasing
And yet, this entire pull request has been rebased since what was in
linux-next on Tuesday (and what would still be there today except I
dropped it because of several conflicts) ... it looks like it was
rebased a week ago, but then never included in your "for-next" branch.
So I supposed it has had your internal testing, at least.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-15 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:25 [GIT PULL] Btrfs updates for 5.10 David Sterba
2020-10-13 16:24 ` pr-tracker-bot
2020-10-15 0:40 ` Stephen Rothwell [this message]
2020-10-15 14:31 ` David Sterba
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=20201015114011.1f5f985a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).