From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] enhance btrfs_raid_array[]
Date: Fri, 27 Apr 2018 09:14:43 +0800 [thread overview]
Message-ID: <bc394a77-a6f0-5b0f-fd37-4e46b3264b1b@oracle.com> (raw)
In-Reply-To: <20180426130129.GR21272@twin.jikos.cz>
On 04/26/2018 09:01 PM, David Sterba wrote:
> On Wed, Apr 25, 2018 at 07:01:41PM +0800, Anand Jain wrote:
>> Cleanup patches as in the individual change log.
>>
>> These patches were sent independently as they aren't related as such,
>> but as I am updating the 1/3 the 2/3 would endup with conflict. So
>> here I am putting all of them together with the conflict fixed at
>> my end. And as such there is no change in 2/3 and 3/3 from its v1.
>>
>> Anand Jain (3):
>> btrfs: kill btrfs_raid_type_names[]
>> btrfs: kill btrfs_raid_group[]
>> btrfs: kill btrfs_raid_mindev_error[]
>
> Added to misc-next, thanks.
> I've reordered the mindev_error before the
> raid_name for better struct packing.
Right. Thanks.
-Anand
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2018-04-27 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 11:01 [PATCH 0/3] enhance btrfs_raid_array[] Anand Jain
2018-04-25 11:01 ` [PATCH v3 1/3] btrfs: kill btrfs_raid_type_names[] Anand Jain
2018-04-25 11:01 ` [PATCH 2/3] btrfs: kill btrfs_raid_group[] Anand Jain
2018-04-25 11:01 ` [PATCH 3/3] btrfs: kill btrfs_raid_mindev_error[] Anand Jain
2018-04-25 14:49 ` [PATCH 0/3] enhance btrfs_raid_array[] Nikolay Borisov
2018-04-26 13:01 ` David Sterba
2018-04-27 1:14 ` Anand Jain [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=bc394a77-a6f0-5b0f-fd37-4e46b3264b1b@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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