From: Neal Gompa <neal@gompa.dev>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
Sweet Tea Dorminy <sweettea-kernel@dorminy.me>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info
Date: Mon, 9 Oct 2023 23:20:32 -0400 [thread overview]
Message-ID: <CAEg-Je-RzwMPhoKGN73QBkKmfxeSDkFi6yJNaBF6Gxz8YBd-Wg@mail.gmail.com> (raw)
In-Reply-To: <20231009034416.GA279961@sol.localdomain>
On Sun, Oct 8, 2023 at 11:44 PM Eric Biggers <ebiggers@kernel.org> wrote:
>
> On Sun, Oct 08, 2023 at 02:11:36AM -0400, Neal Gompa wrote:
> >
> > Looks reasonable to me.
> >
> > Reviewed-by: Neal Gompa <neal@gompa.dev>
> >
>
> Thanks. BTW, please only quote the part that you're replying to.
>
Well, I was replying to the whole patch, so that's why I put my r-b at the end.
--
真実はいつも一つ！/ Always, there's only one truth!
prev parent reply other threads:[~2023-10-10 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 2:57 [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info Eric Biggers
2023-10-08 6:11 ` Neal Gompa
2023-10-09 3:44 ` Eric Biggers
2023-10-10 3:20 ` Neal Gompa [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=CAEg-Je-RzwMPhoKGN73QBkKmfxeSDkFi6yJNaBF6Gxz8YBd-Wg@mail.gmail.com \
--to=neal@gompa.dev \
--cc=ebiggers@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
/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).