[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9662217c-f8c2-4d46-8fff-44609fe36259@wdc.com>
Date: Thu, 14 Sep 2023 09:33:18 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Qu Wenruo <quwenruo.btrfs@....com>, Chris Mason <clm@...com>,
Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>
CC: Christoph Hellwig <hch@....de>,
Naohiro Aota <Naohiro.Aota@....com>, Qu Wenruo <wqu@...e.com>,
Damien Le Moal <dlemoal@...nel.org>,
"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Anand Jain <anand.jain@...cle.com>
Subject: Re: [PATCH v8 02/11] btrfs: read raid-stripe-tree from disk
On 14.09.23 11:27, Qu Wenruo wrote:
>> +static inline struct btrfs_root *btrfs_stripe_tree_root(struct btrfs_fs_info *fs_info)
>> +{
>> + return fs_info->stripe_root;
>> +}
>> +
>
> Do we really need this? IIRC we never have a wrapper or fs_info->fs_root.
This was requested from Josef a while ago, to make the conversion to
per-block-group stripe trees easier. But hch also wanted me to remove it
(and I thought I already did) so lemme get rid of it if Josef doesn't
speak up.
Powered by blists - more mailing lists