From: Waldo Mattias <Mattias.Waldo@saabgroup.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: [PATCH v2] kernel.bbclass: include signing keys when copying files required for module builds
Date: Thu, 25 Aug 2016 09:20:33 +0000 [thread overview]
Message-ID: <1472116833486.43456@saabgroup.com> (raw)
The absence of certs/signing_key.* in $kerneldir made signing of
out-of-tree kernel modules fail (silently). Add copying of these files
during the shared_workdir task.
Signed-off-by: Mattias Waldo <mattias.waldo@saabgroup.com>
---
meta/classes/kernel.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 6e3e81e..2bfd65c 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -295,6 +295,8 @@ do_shared_workdir () {
cp .config $kerneldir/
mkdir -p $kerneldir/include/config
cp include/config/kernel.release $kerneldir/include/config/kernel.release
+ mkdir -p $kerneldir/certs
+ cp certs/signing_key.* $kerneldir/certs
# We can also copy over all the generated files and avoid special cases
# like version.h, but we've opted to keep this small until file creep starts
--
2.9.3
next reply other threads:[~2016-08-25 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 9:20 Waldo Mattias [this message]
2016-08-25 13:51 ` [PATCH v2] kernel.bbclass: include signing keys when copying files required for module builds Burton, Ross
2016-08-25 14:02 ` Waldo Mattias
2016-08-25 15:16 ` Waldo Mattias
2016-08-25 16:47 ` Burton, Ross
2016-08-26 13:37 ` Waldo Mattias
2016-08-27 9:51 ` Waldo Mattias
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=1472116833486.43456@saabgroup.com \
--to=mattias.waldo@saabgroup.com \
--cc=openembedded-core@lists.openembedded.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