From: "Sandoval Gonzalez, Leonardo" <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] staging: add missing import errno to staging_populate_sysroot_dir
Date: Thu, 24 Aug 2017 10:08:45 -0500 [thread overview]
Message-ID: <d81894e2-8a6d-4d14-b74e-a018b6dccdfc@linux.intel.com> (raw)
In-Reply-To: <6D4566C9E07A8D4DAB6F935696920A84244DDB59@ATVIES991UAMSX.ww300.siemens.net>
El 8/24/2017 a las 5:50 AM, Marko, Peter escribió:
> Could this be queued also to pyro branch?
> It's commit ID b1e482ae20b9c714f4089d4da6470d041242e441
better to send another patch tagged with 'pyro' at the subject.
> Thanks,
> Peter
>
>> Fixes error "Exception: NameError: name 'errno' is not defined"
>> during build-sysroots.bb:do_build_target_sysroot
>>
>> Signed-off-by: Marko, Peter <peter.marko@siemens.com>
>> ---
>> meta/classes/staging.bbclass | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass index 162c8e9..9d3d2ad 100644
>> --- a/meta/classes/staging.bbclass
>> +++ b/meta/classes/staging.bbclass
>> @@ -177,6 +177,7 @@ def staging_processfixme(fixme, target, recipesysroot, recipesysrootnative, d):
>> def staging_populate_sysroot_dir(targetsysroot, nativesysroot, native, d):
>> import glob
>> import subprocess
>> + import errno
>>
>> fixme = []
>> postinsts = []
>> --
>> 2.1.4
prev parent reply other threads:[~2017-08-24 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 12:16 [PATCH] staging: add missing import errno to staging_populate_sysroot_dir Marko, Peter
2017-08-23 13:04 ` ✗ patchtest: failure for " Patchwork
2017-08-23 14:03 ` Marko, Peter
2017-08-23 14:56 ` Leonardo Sandoval
2017-08-24 10:50 ` [PATCH] " Marko, Peter
2017-08-24 15:08 ` Sandoval Gonzalez, Leonardo [this message]
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=d81894e2-8a6d-4d14-b74e-a018b6dccdfc@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=Peter.Marko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.