linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Misc btrfs-progs fixes
Date: Fri, 15 Nov 2019 13:22:38 +0100	[thread overview]
Message-ID: <20191115122238.GT3001@twin.jikos.cz> (raw)
In-Reply-To: <20191030122227.28496-1-nborisov@suse.com>

On Wed, Oct 30, 2019 at 02:22:24PM +0200, Nikolay Borisov wrote:
> Here are 2 cleanups and 1 minor fix for mkfs. The gist of the fix is to ensure 
> sub_stripes is always set to 1 when mkfs creates blockgroups with alloc profile 
> different than RAID10. This what kernels does. 
> 
> The other 2 patches are simple cleanups which reduce the number of arguments 
> of btrfs_alloc_data_chunk. 
> 
> Nikolay Borisov (3):
>   btrfs-progs: Initialize sub_stripes to 1 in btrfs_alloc_data_chunk
>   btrfs-progs: Remove type argument from btrfs_alloc_data_chunk
>   btrfs-progs: Remove convert param from btrfs_alloc_data_chunk

Added to devel, thanks.

      parent reply	other threads:[~2019-11-15 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 12:22 [PATCH 0/3] Misc btrfs-progs fixes Nikolay Borisov
2019-10-30 12:22 ` [PATCH 1/3] btrfs-progs: Initialize sub_stripes to 1 in btrfs_alloc_data_chunk Nikolay Borisov
2019-10-30 12:42   ` Qu Wenruo
2019-10-30 12:22 ` [PATCH 2/3] btrfs-progs: Remove type argument from btrfs_alloc_data_chunk Nikolay Borisov
2019-10-30 12:42   ` Qu Wenruo
2019-10-30 12:22 ` [PATCH 3/3] btrfs-progs: Remove convert param " Nikolay Borisov
2019-10-30 12:45   ` Qu Wenruo
2019-11-15 12:22 ` David Sterba [this message]

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=20191115122238.GT3001@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).