From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, clm@fb.com
Subject: [PULL][PATCH 0/9] GFP_NOFS flags cleanup, part 2
Date: Thu, 11 Feb 2016 17:56:52 +0100 [thread overview]
Message-ID: <cover.1455208920.git.dsterba@suse.com> (raw)
Hi,
another portion of the NOFS -> KERNEL conversions, in ioctl handlers and
mount-time functions. Branch will be in my for-next. Please merge to 4.6.
Currently all the simple cases without refactoring seem to be covered. What next
is still going to be determined. There are several classes of functions that
would be fixed in a similar way, eg. the extent state bit wrappers, bios, ulist,
csum calculations.
----------------------------------------------------------------
The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:
Linux 4.5-rc3 (2016-02-07 15:38:30 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/gfp-flags
for you to fetch changes up to 66722f7c059089ad7f11eaa3e27af2321ab1b0e6:
btrfs: switch to kcalloc in btrfs_cmp_data_prepare (2016-02-11 15:19:39 +0100)
----------------------------------------------------------------
David Sterba (9):
btrfs: send: use GFP_KERNEL everywhere
btrfs: reada: use GFP_KERNEL everywhere
btrfs: scrub: use GFP_KERNEL on the submission path
btrfs: let callers of btrfs_alloc_root pass gfp flags
btrfs: fallocate: use GFP_KERNEL
btrfs: readdir: use GFP_KERNEL
btrfs: device add and remove: use GFP_KERNEL
btrfs: extent same: use GFP_KERNEL for page array allocations
btrfs: switch to kcalloc in btrfs_cmp_data_prepare
fs/btrfs/ctree.c | 2 +-
fs/btrfs/dev-replace.c | 2 +-
fs/btrfs/disk-io.c | 21 +++++++++++----------
fs/btrfs/file.c | 6 +++---
fs/btrfs/inode.c | 2 +-
fs/btrfs/ioctl.c | 4 ++--
fs/btrfs/reada.c | 10 +++++-----
fs/btrfs/scrub.c | 24 +++++++++++++-----------
fs/btrfs/send.c | 36 ++++++++++++++++++------------------
fs/btrfs/volumes.c | 9 +++++----
10 files changed, 60 insertions(+), 56 deletions(-)
--
2.7.1
next reply other threads:[~2016-02-11 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 16:56 David Sterba [this message]
2016-02-11 16:56 ` [PATCH 1/9] btrfs: send: use GFP_KERNEL everywhere David Sterba
2016-02-11 16:56 ` [PATCH 2/9] btrfs: reada: " David Sterba
2016-02-11 16:57 ` [PATCH 3/9] btrfs: scrub: use GFP_KERNEL on the submission path David Sterba
2016-02-11 16:57 ` [PATCH 4/9] btrfs: let callers of btrfs_alloc_root pass gfp flags David Sterba
2016-02-11 16:57 ` [PATCH 5/9] btrfs: fallocate: use GFP_KERNEL David Sterba
2016-02-11 16:57 ` [PATCH 6/9] btrfs: readdir: " David Sterba
2016-02-11 16:57 ` [PATCH 7/9] btrfs: device add and remove: " David Sterba
2016-02-11 16:57 ` [PATCH 8/9] btrfs: extent same: use GFP_KERNEL for page array allocations David Sterba
2016-02-11 16:57 ` [PATCH 9/9] btrfs: switch to kcalloc in btrfs_cmp_data_prepare 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=cover.1455208920.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@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).