From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Document some invariants of seed code
Date: Mon, 24 Aug 2020 18:53:28 +0200 [thread overview]
Message-ID: <20200824165328.GO2026@twin.jikos.cz> (raw)
In-Reply-To: <20200812140436.11749-1-nborisov@suse.com>
On Wed, Aug 12, 2020 at 05:04:36PM +0300, Nikolay Borisov wrote:
> Without good understanding of how seed devices works it's hard to grok
> some of what the code in open_seed_devices or btrfs_prepare_sprout does.
>
> Add comments hopefully reducing some of the cognitive load.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
I'll add this patch to the seed list api patchset.
next prev parent reply other threads:[~2020-08-24 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 14:04 [PATCH] btrfs: Document some invariants of seed code Nikolay Borisov
2020-08-24 16:53 ` David Sterba [this message]
2020-08-26 9:13 ` Anand Jain
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=20200824165328.GO2026@twin.jikos.cz \
--to=dsterba@suse.cz \
--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).