From: waxhead <waxhead@dirtcellar.net>
To: dsterba@suse.cz, Neal Gompa <ngompa13@gmail.com>,
David Sterba <dsterba@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] RAID1 with 3- and 4- copies
Date: Sun, 3 Nov 2019 01:35:34 +0100 [thread overview]
Message-ID: <6e3f215f-e3e1-c7f9-c5dc-b89762ef6886@dirtcellar.net> (raw)
In-Reply-To: <20191101150908.GU3001@twin.jikos.cz>
Would GRUB be able to boot from RAID1c34 by treating it as "regular"
RAID1?! If not I think a warning could be useful.
David Sterba wrote:
> On Fri, Nov 01, 2019 at 10:54:45AM -0400, Neal Gompa wrote:
>> What's the reasoning for not submitting this for 5.4? I think the
>> improvements here are definitely worth pulling into the 5.4 kernel
>> release...
>
> Because 5.4 is at rc5, new features are allowed to be merged only during
> the merge window, ie. before 5.4-rc1. Thats more than a month ago. From
> rc1-rcX only regressions or fixes can be applied, so you can see pull
> requests but the subject lines almost always contain 'fix'.
>
> A new feature has to be in the develoment branch at least 2 weeks before
> the merge window opens (for testing), so right now it's the last
> opportunity to get it to 5.5, 5.4 is out of question. No matter how much
> I or users want to get it merged. This is how the linux development
> process works.
>
> The raid1c34 patches are not intrusive and could be backported on top of
> 5.3 because all the preparatory work has been merged already.
>
next prev parent reply other threads:[~2019-11-03 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:13 [PATCH v3 0/4] RAID1 with 3- and 4- copies David Sterba
2019-10-31 15:13 ` [PATCH v2 1/4] btrfs: add support for 3-copy replication (raid1c3) David Sterba
2019-10-31 15:13 ` [PATCH v2 2/4] btrfs: add support for 4-copy replication (raid1c4) David Sterba
2019-10-31 15:13 ` [PATCH v2 3/4] btrfs: add incompat for raid1 with 3, 4 copies David Sterba
2019-10-31 15:13 ` [PATCH v2 4/4] btrfs: drop incompat bit for raid1c34 after last block group is gone David Sterba
2019-10-31 18:43 ` [PATCH] btrfs-progs: add support for raid1c3 and raid1c4 David Sterba
2019-10-31 18:44 ` [PATCH v3 0/4] RAID1 with 3- and 4- copies David Sterba
2019-11-01 14:54 ` Neal Gompa
2019-11-01 15:09 ` David Sterba
2019-11-03 0:35 ` waxhead [this message]
2019-11-04 13:40 ` David Sterba
2019-11-14 5:13 ` Zygo Blaxell
2019-11-15 10:28 ` 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=6e3f215f-e3e1-c7f9-c5dc-b89762ef6886@dirtcellar.net \
--to=waxhead@dirtcellar.net \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa13@gmail.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).