From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: 4.6 compilation error when making signing key
Date: Tue, 17 May 2016 09:37:26 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1605170935450.2008@namei.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1605170927090.1694@namei.org>
CONFIG_MODULE_SIG_KEY="signing_key.pem"
This should be 'certs/signing_key.pem', right?
I'm not sure how it ended up like that -- perhaps something happened in my
next branch (which shares the same .config generally).
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2016-05-16 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 10:08 4.6 compilation error when making signing key James Morris
2016-05-16 11:14 ` David Howells
2016-05-16 23:27 ` James Morris
2016-05-16 23:37 ` James Morris [this message]
2016-05-17 6:56 ` David Howells
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=alpine.LRH.2.20.1605170935450.2008@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).