From: Johannes Thumshirn <jthumshirn@suse.de>
To: David Sterba <dsterba@suse.com>
Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: [PATCH 0/3] btrfs: use offset_in_page and PAGE_ALIGNED
Date: Wed, 5 Dec 2018 15:23:02 +0100 [thread overview]
Message-ID: <20181205142305.15361-1-jthumshirn@suse.de> (raw)
Use the offset_in_page() and PAGE_ALIGNED() macros instead of open-coding them
throughout btrfs.
This series also includes a patch for 'make coccicheck' which is marked as an
RFC and I've CCed Julia in the hoping to get input from her.
Johannes Thumshirn (3):
btrfs: use offset_in_page instead of open-coding it
btrfs: use PAGE_ALIGNED instead of open-coding it
coccinelle: api: add offset_in_page.cocci
fs/btrfs/check-integrity.c | 20 +++----
fs/btrfs/compression.c | 4 +-
fs/btrfs/extent_io.c | 53 +++++++++----------
fs/btrfs/file.c | 4 +-
fs/btrfs/inode.c | 9 ++--
fs/btrfs/send.c | 2 +-
fs/btrfs/volumes.c | 2 +-
scripts/coccinelle/api/offset_in_page.cocci | 81 +++++++++++++++++++++++++++++
8 files changed, 125 insertions(+), 50 deletions(-)
create mode 100644 scripts/coccinelle/api/offset_in_page.cocci
--
2.16.4
next reply other threads:[~2018-12-05 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:23 Johannes Thumshirn [this message]
2018-12-05 14:23 ` [PATCH 1/3] btrfs: use offset_in_page instead of open-coding it Johannes Thumshirn
2018-12-05 14:32 ` Nikolay Borisov
2018-12-05 14:23 ` [PATCH 2/3] btrfs: use PAGE_ALIGNED " Johannes Thumshirn
2018-12-05 14:31 ` Nikolay Borisov
2018-12-05 14:23 ` [RFC PATCH 3/3] coccinelle: api: add offset_in_page.cocci Johannes Thumshirn
2018-12-05 14:46 ` Julia Lawall
2018-12-06 17:11 ` Johannes Thumshirn
2018-12-06 20:15 ` Julia Lawall
2018-12-06 14:54 ` [PATCH 0/3] btrfs: use offset_in_page and PAGE_ALIGNED 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=20181205142305.15361-1-jthumshirn@suse.de \
--to=jthumshirn@suse.de \
--cc=dsterba@suse.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).