From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Document parameters of btrfs_reserve_extent
Date: Wed, 14 Mar 2018 21:08:42 +0100 [thread overview]
Message-ID: <20180314200842.GS32007@twin.jikos.cz> (raw)
In-Reply-To: <21852f3c-f330-ecc8-543d-62c0cc4b66bb@oracle.com>
On Tue, Mar 13, 2018 at 09:56:23PM +0800, Anand Jain wrote:
>
>
> On 03/13/2018 06:22 PM, Nikolay Borisov wrote:
> > This function is the entry to the extent allocator and as such has
> > quite a number of parameters. Some of those have subtle effects on the
> > allocation algorithm. Document the parameters.
> >
> > Signed-off-by: Nikolay Borisov <nborisov@suse.com>
>
> Reviewed-by: Anand Jain <anand.jain@oracle.com>
Added to next, thanks.
next prev parent reply other threads:[~2018-03-14 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 10:22 [PATCH] btrfs: Document parameters of btrfs_reserve_extent Nikolay Borisov
2018-03-13 13:56 ` Anand Jain
2018-03-14 20:08 ` David Sterba [this message]
2018-03-16 18:43 ` Liu Bo
2018-03-16 18:44 ` Nikolay Borisov
2018-03-16 19: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=20180314200842.GS32007@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.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).