linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] fs_info cleanups for volume.c
Date: Sat, 21 Jul 2018 10:08:05 +0800	[thread overview]
Message-ID: <20180721020805.GB575@fnst.localdomain> (raw)
In-Reply-To: <1532104673-28311-1-git-send-email-nborisov@suse.com>

On Fri, Jul 20, 2018 at 07:37:46PM +0300, Nikolay Borisov wrote:
>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

The series looks good to me.

Reviewed-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>

-- 
Thanks,
Lu

>
> 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
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>



  parent reply	other threads:[~2018-07-21  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 16:37 [PATCH 0/7] fs_info cleanups for volume.c Nikolay Borisov
2018-07-20 16:37 ` [PATCH 1/7] btrfs: Remove fs_info argument from btrfs_add_dev_item Nikolay Borisov
2018-07-20 16:37 ` [PATCH 2/7] btrfs: Remove fs_info from btrfs_rm_dev_replace_remove_srcdev Nikolay Borisov
2018-07-20 16:37 ` [PATCH 3/7] btrfs: remove fs_info argument from update_dev_stat_item Nikolay Borisov
2018-07-20 16:37 ` [PATCH 4/7] btrfs: Remove fs_info from btrfs_assign_next_active_device Nikolay Borisov
2018-07-20 16:37 ` [PATCH 5/7] btrfs: Remove fs_info from btrfs_destroy_dev_replace_tgtdev Nikolay Borisov
2018-07-20 16:37 ` [PATCH 6/7] btrfs: Remove fs_info form btrfs_free_chunk Nikolay Borisov
2018-07-20 16:37 ` [PATCH 7/7] btrfs: Remove fs_info from btrfs_finish_chunk_alloc Nikolay Borisov
2018-07-21  2:08 ` Lu Fengqi [this message]
2018-07-23 13:25 ` [PATCH 0/7] fs_info cleanups for volume.c David Sterba
2018-07-24  8:28   ` David Sterba
2018-07-24  8:59     ` Lu Fengqi
2018-07-24 10:41       ` 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=20180721020805.GB575@fnst.localdomain \
    --to=lufq.fnst@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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).