From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "David Howells" <dhowells@redhat.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"David S . Miller" <davem@davemloft.net>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"James Morris" <jmorris@namei.org>,
"Mickaël Salaün" <mic@linux.microsoft.com>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Enable root to update the blacklist keyring
Date: Thu, 14 Jan 2021 06:15:24 +0200 [thread overview]
Message-ID: <X//FXJjQNV/ElHQg@kernel.org> (raw)
In-Reply-To: <X/qJJsVe7+nP+gR6@kernel.org>
On Sun, Jan 10, 2021 at 06:57:10AM +0200, Jarkko Sakkinen wrote:
> On Tue, Jan 05, 2021 at 11:12:57AM +0100, Mickaël Salaün wrote:
> > Jarkko, David, what is the status of this patch series? Do you need help
> > to test it?
>
> Hi, a leave/vacation and the holiday period badly mixed my schedules.
>
> I'm testing this upcoming week.
>
> /Jarkko
❯ git-pw series apply 400795
Applying: certs: Make blacklist_vet_description() more strict
error: sha1 information is lacking or useless (certs/blacklist.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 certs: Make blacklist_vet_description() more strict
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Can you rebase to rc3 and resend?
Also, please add this to the patches 1-3:
Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
Also, 4-5 look good but I hold for testing before acking further.
Thanks, and apologies for such a long wait.
/Jarkko
prev parent reply other threads:[~2021-01-14 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 19:03 [PATCH v2 0/5] Enable root to update the blacklist keyring Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 1/5] certs: Make blacklist_vet_description() more strict Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 2/5] certs: Factor out the blacklist hash creation Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 3/5] certs: Check that builtin blacklist hashes are valid Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 4/5] certs: Allow root user to append signed hashes to the blacklist keyring Mickaël Salaün
2020-12-11 19:03 ` [PATCH v2 5/5] tools/certs: Add print-cert-tbs-hash.sh Mickaël Salaün
2021-01-05 10:12 ` [PATCH v2 0/5] Enable root to update the blacklist keyring Mickaël Salaün
2021-01-10 4:57 ` Jarkko Sakkinen
2021-01-14 4:15 ` Jarkko Sakkinen [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=X//FXJjQNV/ElHQg@kernel.org \
--to=jarkko@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mic@linux.microsoft.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.