From: David Howells <dhowells@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dhowells@redhat.com, LKML <linux-kernel@vger.kernel.org>,
keyrings@vger.kernel.org
Subject: Re: pkcs7_message: taint, no license
Date: Wed, 08 Nov 2017 13:01:26 +0000 [thread overview]
Message-ID: <31511.1510146086@warthog.procyon.org.uk> (raw)
In-Reply-To: <fcecc880-dd7e-7d41-ad27-856ef94a5ae1@infradead.org>
Randy Dunlap <rdunlap@infradead.org> wrote:
> [74785.692410] pkcs7_message: module license 'unspecified' taints kernel.
> [74785.692414] Disabling lock debugging due to kernel taint
Are you particularly using the pkcs#7 parser as a module? I wonder if it
makes most sense to make this and the X.509 options 'bool' rather than
'tristate'.
David
next prev parent reply other threads:[~2017-11-08 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 0:38 Randy Dunlap
2017-11-08 13:01 ` David Howells [this message]
2017-11-08 16:44 ` 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=31511.1510146086@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®