From: Andrej Valek <andrej.valek@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] kernel-devsrc: fix searching for non-existing
Date: Wed, 26 Sep 2018 15:28:47 +0200 [thread overview]
Message-ID: <20180926132848.6632-1-andrej.valek@siemens.com> (raw)
In-Reply-To: <7f369514-092a-6a76-0262-ac9a84309b10@siemens.com>
I have tested your proposal fix and it works.
I have removed the _setscene, because _sysroot is enough.
To make recipe consistent, I have also changed the rest of [noexec]s.
Andrej Valek (1):
kernel-devsrc: fix searching for non-existing manifest files
meta/recipes-kernel/linux/kernel-devsrc.bb | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.11.0
next prev parent reply other threads:[~2018-09-26 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:51 SDK and out of tree modules Andrej Valek
2018-09-25 15:22 ` richard.purdie
2018-09-26 12:22 ` Andrej Valek
2018-09-26 12:27 ` richard.purdie
2018-09-26 13:28 ` Andrej Valek [this message]
2018-09-26 13:28 ` [PATCH 1/1] kernel-devsrc: fix searching for non-existing manifest files Andrej Valek
2018-09-26 15:54 ` Khem Raj
2018-09-26 22:30 ` Richard Purdie
2018-09-26 23:12 ` Richard Purdie
2018-09-26 23:52 ` Khem Raj
2018-09-27 5:55 ` Andrej Valek
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=20180926132848.6632-1-andrej.valek@siemens.com \
--to=andrej.valek@siemens.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