From: Nikolay Borisov <nborisov@suse.com>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
David Sterba <dsterba@suse.cz>
Cc: Josef Bacik <josef@toxicpanda.com>,
"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v5 3/7] btrfs: let btrfs_read_dev_super() return a btrfs_super_block
Date: Fri, 7 Feb 2020 12:12:43 +0200 [thread overview]
Message-ID: <0cf848b0-dbca-a7b3-d58f-a20066302b5f@suse.com> (raw)
In-Reply-To: <20200207072005.22867-4-johannes.thumshirn@wdc.com>
On 7.02.20 г. 9:20 ч., Johannes Thumshirn wrote:
> Let btrfs_read_dev_super() return a 'struct btrfs_super_block' and
> btrfs_release_disk_super() take a 'struct btrfs_disk_super' as well.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
next prev parent reply other threads:[~2020-02-07 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 7:19 [PATCH v5 0/7] btrfs: remove buffer heads form superblock handling Johannes Thumshirn
2020-02-07 7:19 ` [PATCH v5 1/7] btrfs: Export btrfs_release_disk_super Johannes Thumshirn
2020-02-07 7:20 ` [PATCH v5 2/7] btrfs: use the page-cache for super block reading Johannes Thumshirn
2020-02-07 10:08 ` Nikolay Borisov
2020-02-07 7:20 ` [PATCH v5 3/7] btrfs: let btrfs_read_dev_super() return a btrfs_super_block Johannes Thumshirn
2020-02-07 10:12 ` Nikolay Borisov [this message]
2020-02-07 7:20 ` [PATCH v5 4/7] btrfs: use BIOs instead of buffer_heads from superblock writeout Johannes Thumshirn
2020-02-07 7:20 ` [PATCH v5 5/7] btrfs: remove btrfsic_submit_bh() Johannes Thumshirn
2020-02-07 7:20 ` [PATCH v5 6/7] btrfs: remove buffer_heads from btrfsic_process_written_block() Johannes Thumshirn
2020-02-07 10:17 ` Nikolay Borisov
2020-02-07 7:20 ` [PATCH v5 7/7] btrfs: remove buffer_heads form superblock mirror integrity checking Johannes Thumshirn
2020-02-07 10:59 ` Nikolay Borisov
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=0cf848b0-dbca-a7b3-d58f-a20066302b5f@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.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