From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/10] btrfs: relocation: Refactor build_backref_tree()
Date: Sat, 29 Feb 2020 09:00:43 +0800 [thread overview]
Message-ID: <99a7a002-65bb-6077-7303-c4076c34e05e@gmx.com> (raw)
In-Reply-To: <20200228154555.GN2902@twin.jikos.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]
On 2020/2/28 下午11:45, David Sterba wrote:
> On Wed, Feb 26, 2020 at 01:56:42PM +0800, Qu Wenruo wrote:
>> This branch can be fetched from github:
>> https://github.com/adam900710/linux/tree/backref_cache_new
>
> This is based on v5.6-rc1, you should base on something more recent.
> There are many non-trivial conflicts at patch 5 so I stopped there but
> if you and I like to get the pathes merged, the branch needs to be in a
> state where it's not that hard to apply the patches.
Because it looks like current misc-next is not a good place to do proper
testing, and it's undergoing frequent updates.
Thus I choose the latest rc when I started the development.
Currently the branch is only for review and my local testing, I just
want to make sure that everything works fine before rebasing them to
misc-next.
Anyway, next time I'll mention the basis, and explicitly shows that I'll
do the rebase (and retest) if you want to try merge.
Thanks,
Qu
>
> Minor conflicts are expected, like obvious differences in context or
> renames, there are tools that can deal with that automatically (I use
> wiggle).
>
> The branch also contains unrelated patches to the backref code, some of
> them either upstream or in misc-next. All of that makes it unnecessarily
> hard to get the patches to for-next when the time comes (reviews, patch
> backlog processed).
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-29 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 5:56 [PATCH 00/10] btrfs: relocation: Refactor build_backref_tree() Qu Wenruo
2020-02-26 5:56 ` [PATCH 01/10] btrfs: backref: Introduce the skeleton of btrfs_backref_iter Qu Wenruo
2020-02-26 5:56 ` [PATCH 02/10] btrfs: backref: Implement btrfs_backref_iter_next() Qu Wenruo
2020-02-26 5:56 ` [PATCH 03/10] btrfs: relocation: Use btrfs_backref_iter infrastructure Qu Wenruo
2020-02-26 5:56 ` [PATCH 04/10] btrfs: relocation: Rename mark_block_processed() and __mark_block_processed() Qu Wenruo
2020-02-26 13:56 ` Nikolay Borisov
2020-02-26 5:56 ` [PATCH 05/10] btrfs: relocation: Refactor tree backref processing into its own function Qu Wenruo
2020-02-26 5:56 ` [PATCH 06/10] btrfs: relocation: Use wrapper to replace open-coded edge linking Qu Wenruo
2020-02-26 5:56 ` [PATCH 07/10] btrfs: relocation: Specify essential members for alloc_backref_node() Qu Wenruo
2020-02-26 5:56 ` [PATCH 08/10] btrfs: relocation: Remove the open-coded goto loop for breadth-first search Qu Wenruo
2020-02-26 5:56 ` [PATCH 09/10] btrfs: relocation: Refactor the finishing part of upper linkage into finish_upper_links() Qu Wenruo
2020-02-26 5:56 ` [PATCH 10/10] btrfs: relocation: Refactor the useless nodes handling into its own function Qu Wenruo
2020-02-28 15:45 ` [PATCH 00/10] btrfs: relocation: Refactor build_backref_tree() David Sterba
2020-02-29 1:00 ` Qu Wenruo [this message]
2020-03-02 20:26 ` 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=99a7a002-65bb-6077-7303-c4076c34e05e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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