From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com,
linux-fsdevel@vger.kernel.org
Cc: ebiggers@kernel.org, linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH v4 00/46] btrfs: add fscrypt support
Date: Fri, 1 Dec 2023 17:15:50 -0500 [thread overview]
Message-ID: <20231201221550.GA4134816@perftesting> (raw)
In-Reply-To: <cover.1701468305.git.josef@toxicpanda.com>
On Fri, Dec 01, 2023 at 05:10:57PM -0500, Josef Bacik wrote:
> Hello,
>
> v3 can be found here
>
> https://lore.kernel.org/linux-btrfs/cover.1697480198.git.josef@toxicpanda.com/
Sorry Eric, it's been a long week and I forgot how to use email, didn't cc you
or linux-fscrypt on this series. It's on fsdevel and the btrfs list. Thanks,
Josef
next parent reply other threads:[~2023-12-01 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1701468305.git.josef@toxicpanda.com>
2023-12-01 22:15 ` Josef Bacik [this message]
2024-04-09 23:42 ` [PATCH v4 00/46] btrfs: add fscrypt support Eric Biggers
2024-04-11 18:45 ` Josef Bacik
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=20231201221550.GA4134816@perftesting \
--to=josef@toxicpanda.com \
--cc=ebiggers@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).