Re: [PATCH v6 00/43] btrfs: add fscrypt support
Neal Gompa <[email protected]> Wed, 15 Apr 2026 01:30:15 -0400
| Newsgroups | org.kernel.vger.linux-fscrypt,org.kernel.vger.linux-block,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAEg-Je9XevtRv1VLPCQtog6+UrLL32ZWY_TzXVd8mU5Vnp+Nzg@mail.gmail.com> |
On Sat, Feb 28, 2026 at 2:57 AM Daniel Vacek <[email protected]> wrote: > > On Fri, 27 Feb 2026 at 23:26, Neal Gompa <[email protected]> wrote: > > On Fri, Feb 27, 2026 at 10:55 AM Daniel Vacek <[email protected]> wrote: > > > On Sat, 21 Feb 2026 at 21:56, Eric Biggers <[email protected]> wrote: > > > > On Fri, Feb 06, 2026 at 07:22:32PM +0100, Daniel Vacek wrote: > > > > > Hello, > > > > > > > > > > These are the remaining parts from former series [1] from Omar, Sweet Tea > > > > > and Josef. Some bits of it were split into the separate set [2] before. > > > > > > > > > > Notably, at this stage encryption is not supported with RAID5/6 setup > > > > > and send is also isabled for now. > > > > > > > > Where does this series apply to? There's no base-commit or git tree, > > > > and it doesn't apply to mainline or btrfs/for-next. > > > > > > Hi Eric, > > > > > > My apologies, I did not explicitly mention the base. I'll do it next time. > > > This was based on for-next @20260127 (commit 80dbfe6512d9c). > > > Since then, some changes occurred that will require additional > > > touches. No wonder it does not apply anymore. > > > > > > > When you make your next revision, can you also provide a tag or branch > > that I can use to grab the patches for testing? It would be easier for > > me than trying to yoink them down from the emails with how many of > > them there are... > > Sure > Ping to ask about the refreshed patch set. With 7.0 out the door, it'd be nice to have an updated set with feedback addressed... -- 真実はいつも一つ!/ Always, there's only one truth!