From: Eric Biggers <ebiggers@kernel.org>
To: Victor Hsieh <victorhsieh@google.com>
Cc: fsverity@lists.linux.dev, keyrings@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] fsverity: skip PKCS#7 parser when keyring is empty
Date: Tue, 1 Aug 2023 21:15:45 -0700 [thread overview]
Message-ID: <20230802041545.GA1543@sol.localdomain> (raw)
In-Reply-To: <CAFCauYMrQf4TJJ+8atPrsihDa9+nKb5zn-rCKqB3081d8ZvZoA@mail.gmail.com>
On Tue, Aug 01, 2023 at 09:07:44AM -0700, Victor Hsieh wrote:
> Should the whole use of "d" be moved into the else block?
In v2, changed to use an early return instead.
- Eric
next prev parent reply other threads:[~2023-08-02 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 5:07 [PATCH] fsverity: skip PKCS#7 parser when keyring is empty Eric Biggers
2023-08-01 16:07 ` Victor Hsieh
2023-08-02 4:15 ` Eric Biggers [this message]
2023-08-01 18:53 ` Jarkko Sakkinen
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=20230802041545.GA1543@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=keyrings@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=victorhsieh@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).