From: David Howells <dhowells@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dhowells@redhat.com, Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 26 (task_struct: cached_requested_key)
Date: Wed, 26 Jun 2019 20:59:32 +0100 [thread overview]
Message-ID: <13370.1561579172@warthog.procyon.org.uk> (raw)
In-Reply-To: <1d868a7a-0a15-e2b1-d73b-13d9229855ad@infradead.org>
Randy Dunlap <rdunlap@infradead.org> wrote:
> Multiple build errors like this when CONFIG_KEYS is not set/enabled:
> (this was seen on one i386 build)
Ah - I forgot to make CONFIG_KEYS_REQUEST_CACHE depend on CONFIG_KEYS.
David
next prev parent reply other threads:[~2019-06-26 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:16 linux-next: Tree for Jun 26 Stephen Rothwell
2019-06-26 16:01 ` linux-next: Tree for Jun 26 (task_struct: cached_requested_key) Randy Dunlap
2019-06-26 19:59 ` David Howells [this message]
2019-06-26 18:35 ` linux-next: Tree for Jun 26 (security/integrity/ima/) Randy Dunlap
2019-06-27 13:02 ` Mimi Zohar
2019-06-27 13:29 ` David Howells
2019-06-27 15:08 ` 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=13370.1561579172@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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