From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Valek, Andrej" <andrej.valek@siemens.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks
Date: Thu, 26 Nov 2020 14:51:38 +0000 [thread overview]
Message-ID: <2c0da7ad07d9339449faa6842740edc5471ecf83.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB8PR10MB39775710E456F17F2FAE85A792F90@DB8PR10MB3977.EURPRD10.PROD.OUTLOOK.COM>
On Thu, 2020-11-26 at 14:44 +0000, Valek, Andrej wrote:
> No it's not a leftover. I've just copied it from kernel.bbclass,
> where this task is written correctly. But you can change it to
> previous version I guess.
I'm trying to work out why we need the extra dependencies when the
tasks are empty.
I can see how adding the inherit would help, I'm less sure how adding
the deploy task after the others does though.
Cheers,
Richard
next prev parent reply other threads:[~2020-11-26 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 10:17 Error when building eSDK for a "linux-dummy" Andrej Valek
2020-11-25 15:42 ` Khem Raj
2020-11-25 16:54 ` [OE-core][PATCH] kernel-dummy: fix executing unexpected tasks Andrej Valek
2020-11-25 17:02 ` [yocto] " Paul Barker
2020-11-25 17:05 ` Bruce Ashfield
2020-11-25 17:20 ` [OE-core][PATCH v2] " Andrej Valek
2020-11-26 14:37 ` Richard Purdie
2020-11-26 14:44 ` Andrej Valek
2020-11-26 14:51 ` Richard Purdie [this message]
2020-11-26 15:10 ` Andrej Valek
2020-11-29 7:49 ` [OE-core][PATCH v3] " 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=2c0da7ad07d9339449faa6842740edc5471ecf83.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@lists.yoctoproject.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