From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: bo.li.liu@oracle.com, David Sterba <dsterba@suse.com>
Subject: [PATCH 0/3] Cleanup sector_t
Date: Fri, 6 Oct 2017 14:29:53 +0200 [thread overview]
Message-ID: <cover.1507292872.git.dsterba@suse.com> (raw)
David Sterba (3):
btrfs: scrub: get rid of sector_t
btrfs: rename page offset parameter in submit_extent_page
btrfs: get rid of sector_t and use u64 offset in submit_extent_page
fs/btrfs/extent_io.c | 31 ++++++++++++++++---------------
fs/btrfs/scrub.c | 14 +++++++-------
2 files changed, 23 insertions(+), 22 deletions(-)
--
2.14.0
next reply other threads:[~2017-10-06 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 12:29 David Sterba [this message]
2017-10-06 12:29 ` [PATCH 1/3] btrfs: scrub: get rid of sector_t David Sterba
2017-10-06 15:22 ` Edmund Nadolski
2017-10-06 15:48 ` David Sterba
2017-10-07 0:15 ` Liu Bo
2017-10-06 12:29 ` [PATCH 2/3] btrfs: rename page offset parameter in submit_extent_page David Sterba
2017-10-07 0:11 ` Liu Bo
2017-10-06 12:30 ` [PATCH 3/3] btrfs: get rid of sector_t and use u64 offset " David Sterba
2017-10-07 0:21 ` Liu Bo
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=cover.1507292872.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=bo.li.liu@oracle.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).