From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for Feb 15 (certs/blacklist.c)
Date: Mon, 15 Feb 2021 09:13:24 -0800 [thread overview]
Message-ID: <bc2c24e3-ed68-2521-0bf4-a1f6be4a895d@infradead.org> (raw)
In-Reply-To: <20210215203421.43cc2a4a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
On 2/15/21 1:34 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210212:
>
on x86_64:
ld: certs/blacklist.o: in function `is_key_on_revocation_list':
blacklist.c:(.text+0x20d): undefined reference to `pkcs7_validate_trust'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r7843.gz --]
[-- Type: application/gzip, Size: 35697 bytes --]
next prev parent reply other threads:[~2021-02-15 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 9:34 linux-next: Tree for Feb 15 Stephen Rothwell
2021-02-15 17:13 ` Randy Dunlap [this message]
2021-02-15 17:35 ` linux-next: Tree for Feb 15 (CXL on i386) Randy Dunlap
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=bc2c24e3-ed68-2521-0bf4-a1f6be4a895d@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).