From: Omar Sandoval <osandov@osandov.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/9] btrfs: miscellaneous cleanups
Date: Tue, 10 Dec 2019 10:50:38 -0800 [thread overview]
Message-ID: <20191210185038.GD204474@vader> (raw)
In-Reply-To: <20191210184744.GH3929@twin.jikos.cz>
On Tue, Dec 10, 2019 at 07:47:44PM +0100, David Sterba wrote:
> On Mon, Dec 02, 2019 at 05:34:16PM -0800, Omar Sandoval wrote:
> > This series includes several cleanups. Patches 1-3 are the standalone
> > cleanups from my RWF_ENCODED series [1] (as requested by Dave). Patches
> > 4-8 clean up code rot in the writepage codepath. Patch 9 is a trivial
> > cleanup in find_free_extent.
> >
> > Based on misc-next.
> >
> > Thanks!
> >
> > 1: https://lore.kernel.org/linux-btrfs/cover.1574273658.git.osandov@fb.com/
> >
> > Omar Sandoval (9):
> > btrfs: get rid of trivial __btrfs_lookup_bio_sums() wrappers
> > btrfs: remove dead snapshot-aware defrag code
> > btrfs: make btrfs_ordered_extent naming consistent with
> > btrfs_file_extent_item
> > btrfs: remove unnecessary pg_offset assignments in
> > __extent_writepage()
> > btrfs: remove trivial goto label in __extent_writepage()
> > btrfs: remove redundant i_size check in __extent_writepage_io()
> > btrfs: drop create parameter to btrfs_get_extent()
> > btrfs: simplify compressed/inline check in __extent_writepage_io()
> > btrfs: remove struct find_free_extent.ram_bytes
>
> Added to misc-next with minor fixups, thanks.
Thank you!
prev parent reply other threads:[~2019-12-10 18:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 1:34 [PATCH 0/9] btrfs: miscellaneous cleanups Omar Sandoval
2019-12-03 1:34 ` [PATCH 1/9] btrfs: get rid of trivial __btrfs_lookup_bio_sums() wrappers Omar Sandoval
2019-12-03 8:36 ` Johannes Thumshirn
2019-12-10 17:12 ` David Sterba
2019-12-10 18:24 ` Omar Sandoval
2019-12-10 18:26 ` David Sterba
2019-12-10 18:37 ` [PATCH] btrfs: get rid of at_offset parameter to btrfs_lookup_bio_sums() Omar Sandoval
2019-12-03 1:34 ` [PATCH 2/9] btrfs: remove dead snapshot-aware defrag code Omar Sandoval
2019-12-03 8:38 ` Johannes Thumshirn
2019-12-10 17:22 ` David Sterba
2019-12-03 1:34 ` [PATCH 3/9] btrfs: make btrfs_ordered_extent naming consistent with btrfs_file_extent_item Omar Sandoval
2019-12-03 9:51 ` Johannes Thumshirn
2019-12-10 18:22 ` David Sterba
2019-12-10 18:32 ` Omar Sandoval
2019-12-10 18:48 ` David Sterba
2019-12-03 1:34 ` [PATCH 4/9] btrfs: remove unnecessary pg_offset assignments in __extent_writepage() Omar Sandoval
2019-12-03 12:59 ` Johannes Thumshirn
2019-12-03 1:34 ` [PATCH 5/9] btrfs: remove trivial goto label " Omar Sandoval
2019-12-03 13:06 ` Johannes Thumshirn
2019-12-03 1:34 ` [PATCH 6/9] btrfs: remove redundant i_size check in __extent_writepage_io() Omar Sandoval
2019-12-10 17:45 ` David Sterba
2019-12-03 1:34 ` [PATCH 7/9] btrfs: drop create parameter to btrfs_get_extent() Omar Sandoval
2019-12-03 7:47 ` Omar Sandoval
2019-12-03 1:34 ` [PATCH 8/9] btrfs: simplify compressed/inline check in __extent_writepage_io() Omar Sandoval
2019-12-03 13:17 ` Johannes Thumshirn
2019-12-03 1:34 ` [PATCH 9/9] btrfs: remove struct find_free_extent.ram_bytes Omar Sandoval
2019-12-03 13:27 ` Johannes Thumshirn
2019-12-03 18:01 ` Omar Sandoval
2019-12-10 18:47 ` [PATCH 0/9] btrfs: miscellaneous cleanups David Sterba
2019-12-10 18:50 ` Omar Sandoval [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=20191210185038.GD204474@vader \
--to=osandov@osandov.com \
--cc=dsterba@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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).