From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] btrfs: btrfs_get_extent() cleanup for inline extents
Date: Thu, 27 Oct 2022 16:46:10 +0200 [thread overview]
Message-ID: <20221027144610.GW5824@twin.jikos.cz> (raw)
In-Reply-To: <20221025140851.GL5824@twin.jikos.cz>
On Tue, Oct 25, 2022 at 04:08:51PM +0200, David Sterba wrote:
> > v2:
> > - Do better patch split for bisection with better reason
> >
> > - Put the selftest to the first to help bisection
> > Or we may hit ASSERT() during selftest.
> >
> > Qu Wenruo (5):
> > btrfs: selftests: remove impossible inline extent at non-zero file
> > offset
> > btrfs: make inline extent read calculation much simpler
> > btrfs: do not reset extent map members for inline extents read
> > btrfs: remove the @new_inline argument from
> > btrfs_extent_item_to_extent_map()
> > btrfs: extract the inline extent read code into its own function
>
> I did a quick review, code looks ok for inclusion to for-next.
Moved to misc-next, thanks.
prev parent reply other threads:[~2022-10-27 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 7:28 [PATCH v2 0/5] btrfs: btrfs_get_extent() cleanup for inline extents Qu Wenruo
2022-09-16 7:28 ` [PATCH v2 1/5] btrfs: selftests: remove impossible inline extent at non-zero file offset Qu Wenruo
2022-09-16 7:28 ` [PATCH v2 2/5] btrfs: make inline extent read calculation much simpler Qu Wenruo
2022-09-16 7:28 ` [PATCH v2 3/5] btrfs: do not reset extent map members for inline extents read Qu Wenruo
2022-09-16 7:28 ` [PATCH v2 4/5] btrfs: remove the @new_inline argument from btrfs_extent_item_to_extent_map() Qu Wenruo
2022-09-16 7:28 ` [PATCH v2 5/5] btrfs: extract the inline extent read code into its own function Qu Wenruo
2022-10-25 14:11 ` David Sterba
2022-10-25 14:08 ` [PATCH v2 0/5] btrfs: btrfs_get_extent() cleanup for inline extents David Sterba
2022-10-27 14:46 ` David Sterba [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=20221027144610.GW5824@twin.jikos.cz \
--to=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