From: Marco <koansoftware@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
Marco Cavallini <m.cavallini@koansoftware.com>
Subject: Re: [oe] [meta-networking][PATCH v2] bluepy_git.bb: Added recipe for BluePy Python interface to Bluetooth LE on Linux (v2)
Date: Wed, 20 Oct 2021 14:07:03 +0200 [thread overview]
Message-ID: <41085dec-5948-b1c1-56ea-b10004e07939@gmail.com> (raw)
In-Reply-To: <CAMKF1sqso8ZijOMFVoEYWZG70W1rAK9ih3AthPOvjV3_A+q-sg@mail.gmail.com>
On 20/10/21 13:45, Khem Raj wrote:
> fails during install now on musl/x86 arm/glibc
>
> https://errors.yoctoproject.org/Errors/Details/613446/
> https://errors.yoctoproject.org/Errors/Details/613456/
>
Hi Khem,
I diligently followed the instructions on the site
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
To correct the errors you reported to me previously, I installed the
'master' version of Poky + Openembedded and recompiled everything
without errors and I re-sent the v2 patch.
At this point I no longer know what the requirements are for submitting
a patch.
Do you need to pass any series of tests?
Which one?
How do I reproduce them locally?
Thank you
--
Marco
next prev parent reply other threads:[~2021-10-20 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 13:19 [meta-networking][PATCH v2] bluepy_git.bb: Added recipe for BluePy Python interface to Bluetooth LE on Linux (v2) Marco Cavallini
2021-10-20 11:45 ` [oe] " Khem Raj
2021-10-20 12:07 ` Marco [this message]
2021-10-20 14:10 ` Khem Raj
2021-10-20 17:02 ` Martin Jansa
[not found] ` <16AFCBDEF9895FF9.31449@lists.openembedded.org>
2021-10-20 17:05 ` Martin Jansa
2021-10-20 17:07 ` Martin Jansa
2021-10-20 17:23 ` Khem Raj
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=41085dec-5948-b1c1-56ea-b10004e07939@gmail.com \
--to=koansoftware@gmail.com \
--cc=m.cavallini@koansoftware.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).