From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mattias Waldo <mattias.waldo@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4] kernel.bbclass: include signing keys when copying files required for module builds
Date: Tue, 30 Aug 2016 23:45:21 +0100 [thread overview]
Message-ID: <1472597121.29583.59.camel@linuxfoundation.org> (raw)
In-Reply-To: <1472237886-7172-1-git-send-email-mattias.waldo@gmail.com>
On Fri, 2016-08-26 at 20:58 +0200, Mattias Waldo wrote:
> 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(+)
Sadly this breaks the build when you don't have any keys:
e.g.: https://autobuilder.yoctoproject.org/main/builders/build-applianc
e/builds/892/steps/BuildImages_1/logs/stdio
but there were many many other failures :(
Cheers,
Richard
next prev parent reply other threads:[~2016-08-30 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 18:58 [PATCH v4] kernel.bbclass: include signing keys when copying files required for module builds Mattias Waldo
2016-08-30 22:45 ` Richard Purdie [this message]
2016-09-01 14:40 ` Mattias Waldo
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=1472597121.29583.59.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mattias.waldo@gmail.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