summaryrefslogtreecommitdiff
path: root/Kconfig
diff options
context:
space:
mode:
authorDavid Woodhouse <David.Woodhouse@intel.com>2015-08-14 16:17:16 +0100
committerDavid Howells <dhowells@redhat.com>2015-08-14 16:32:52 +0100
commit3ee550f12c1529a023f71c9b5becb3351911047b (patch)
treea60711f8662b42d5720b90567daf718cb90eca93 /Kconfig
parent62172c81f2d6c2311284467d6aaa00bd8967e136 (diff)
downloadlwn-3ee550f12c1529a023f71c9b5becb3351911047b.tar.gz
lwn-3ee550f12c1529a023f71c9b5becb3351911047b.zip
modsign: Handle signing key in source tree
Since commit 1329e8cc69 ("modsign: Extract signing cert from CONFIG_MODULE_SIG_KEY if needed"), the build system has carefully coped with the signing key being specified as a relative path in either the source or or the build trees. However, the actual signing of modules has not worked if the filename is relative to the source tree. Fix that by moving the config_filename helper into scripts/Kbuild.include so that it can be used from elsewhere, and then using it in the top-level Makefile to find the signing key file. Kill the intermediate $(MODPUBKEY) and $(MODSECKEY) variables too, while we're at it. There's no need for them. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions