From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:49908 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1733128AbeGTR1A (ORCPT ); Fri, 20 Jul 2018 13:27:00 -0400 Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 6B843AD3E for ; Fri, 20 Jul 2018 16:37:55 +0000 (UTC) From: Nikolay Borisov To: linux-btrfs@vger.kernel.org Cc: Nikolay Borisov Subject: [PATCH 0/7] fs_info cleanups for volume.c Date: Fri, 20 Jul 2018 19:37:46 +0300 Message-Id: <1532104673-28311-1-git-send-email-nborisov@suse.com> Sender: linux-btrfs-owner@vger.kernel.org List-ID: Here are a bunch of patches which cleanup extraneous fs_info parameters to function which already take a structure that holds a reference to the fs_info. Except for patches 4 and 5, everything else is correct - due to those functions always taking a transaction. 4 and 5 in turn reference the fs_info from struct btrfs_device. Inspecting the callers I managed to convince myself that those function are always called with well-formed btrfs_device i.e one which has its fs_info member initialised. Reviewers might want to pay extra attention to that but otherwise they are trivial. Nikolay Borisov (7): btrfs: Remove fs_info argument from btrfs_add_dev_item btrfs: Remove fs_info from btrfs_rm_dev_replace_remove_srcdev btrfs: remove fs_info argument from update_dev_stat_item btrfs: Remove fs_info from btrfs_assign_next_active_device btrfs: Remove fs_info from btrfs_destroy_dev_replace_tgtdev btrfs: Remove fs_info form btrfs_free_chunk btrfs: Remove fs_info from btrfs_finish_chunk_alloc fs/btrfs/dev-replace.c | 10 +++++----- fs/btrfs/extent-tree.c | 5 ++--- fs/btrfs/volumes.c | 49 +++++++++++++++++++++++-------------------------- fs/btrfs/volumes.h | 16 ++++++---------- 4 files changed, 36 insertions(+), 44 deletions(-) -- 2.7.4