public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: David Sterba <dsterba@suse.cz>
Cc: Wang Yugui <wangyugui@e16-tech.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: please rebase the patch queue-6.1(btrfs: fix an error handling path in btrfs_defrag_leaves)
Date: Tue, 10 Jan 2023 10:26:07 -0500	[thread overview]
Message-ID: <Y72Dj4ZbNome2aKJ@sashalap> (raw)
In-Reply-To: <20230110143008.GB11562@twin.jikos.cz>

On Tue, Jan 10, 2023 at 03:30:08PM +0100, David Sterba wrote:
>On Tue, Jan 10, 2023 at 04:42:35PM +0800, Wang Yugui wrote:
>> Hi,
>>
>> > On Tue, Jan 10, 2023 at 12:38:14PM +0800, Wang Yugui wrote:
>> > > Hi, Sasha Levin
>> > >
>> > > please rebase the patch queue-6.1(btrfs: fix an error handling path in btrfs_defrag_leaves)
>> > > just like queue-6.0, and then drop its 8 depency patches.
>> > >
>> > > the 2 of 8 depency patches are file rename, so it will make later depency patch become
>> > > difficult?
>> > > #btrfs-move-btrfs_get_block_group-helper-out-of-disk-.patch
>> > > #btrfs-move-flush-related-definitions-to-space-info.h.patch
>> > > #btrfs-move-btrfs_print_data_csum_error-into-inode.c.patch
>> > > #btrfs-move-fs-wide-helpers-out-of-ctree.h.patch
>> > > #btrfs-move-assert-helpers-out-of-ctree.h.patch
>> > > #btrfs-move-the-printk-helpers-out-of-ctree.h.patch
>> > > #**btrfs-rename-struct-funcs.c-to-accessors.c.patch
>> > > #**btrfs-rename-tree-defrag.c-to-defrag.c.patch
>> > >
>> > > and the patch(btrfs: fix an error handling path in btrfs_defrag_leaves) is small,
>> > > so a rebase will be a good choice.
>> >
>> > I do not understand, sorry, we can not rebase anything, that's not how
>> > our patch queue works.
>> >
>> > So what exactly do you want to see changed?  What patches dropped?  And
>> > what added?
>>
>> What I suggest:
>>
>> 1)replace queue-6.1/btrfs-fix-an-error-handling-path-in-btrfs_defrag_lea.patch
>>         with queue-6.0/btrfs-fix-an-error-handling-path-in-btrfs_defrag_lea.patch
>>
>> 2) drop pathes in queue-6.1/
>> btrfs-move-btrfs_get_block_group-helper-out-of-disk-.patch
>> btrfs-move-flush-related-definitions-to-space-info.h.patch
>> btrfs-move-btrfs_print_data_csum_error-into-inode.c.patch
>> btrfs-move-fs-wide-helpers-out-of-ctree.h.patch
>> btrfs-move-assert-helpers-out-of-ctree.h.patch
>> btrfs-move-the-printk-helpers-out-of-ctree.h.patch
>> btrfs-rename-struct-funcs.c-to-accessors.c.patch
>> btrfs-rename-tree-defrag.c-to-defrag.c.patch
>
>Right, I'd rather not add all the code moving patches to stable though I
>understand that it could ease backporting. Many stable backports need to
>be adapted to versions before/after the code moves so the work has to be
>done anyway.

Okay, done.

-- 
Thanks,
Sasha

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  4:38 please rebase the patch queue-6.1(btrfs: fix an error handling path in btrfs_defrag_leaves) Wang Yugui
2023-01-10  7:57 ` Greg KH
2023-01-10  8:42   ` Wang Yugui
2023-01-10 14:30     ` David Sterba
2023-01-10 15:26       ` Sasha Levin [this message]

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=Y72Dj4ZbNome2aKJ@sashalap \
    --to=sashal@kernel.org \
    --cc=dsterba@suse.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wangyugui@e16-tech.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