From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maxin B. John" <maxin.john@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] i2c-tools: upgrade to 4.0
Date: Sat, 09 Dec 2017 17:17:53 +0000 [thread overview]
Message-ID: <1512839873.19417.120.camel@linuxfoundation.org> (raw)
In-Reply-To: <1512838668.19417.119.camel@linuxfoundation.org>
On Sat, 2017-12-09 at 16:57 +0000, Richard Purdie wrote:
> On Thu, 2017-12-07 at 15:22 +0200, Maxin B. John wrote:
> >
> > Update the SRC_URI to point to kernel.org location where
> > i2c-tools is hosted these days.
> >
> > Remove Modules.mk since it was used for deprecated binaries
> > (eepromer, eeprom)
> >
> > Signed-off-by: Maxin B. John <maxin.john@intel.com>
> > ---
> > meta/recipes-devtools/i2c-tools/files/Module.mk | 72 ----------
> > --
> > ----------
> > .../{i2c-tools_3.1.2.bb => i2c-tools_4.0.bb} | 14 ++---
> > 2 files changed, 5 insertions(+), 81 deletions(-)
> > delete mode 100644 meta/recipes-devtools/i2c-tools/files/Module.mk
> > rename meta/recipes-devtools/i2c-tools/{i2c-tools_3.1.2.bb => i2c-
> > tools_4.0.bb} (64%)
> Fails on musl sadly:
>
> https://autobuilder.yocto.io/builders/nightly-musl/builds/643/steps/B
> uildImages/logs/stdio
and on glibc qemux86-64:
https://autobuilder.yocto.io/builders/nightly-world/builds/622
Build race?
Cheers,
Richard
next prev parent reply other threads:[~2017-12-09 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 13:22 [PATCH] i2c-tools: upgrade to 4.0 Maxin B. John
2017-12-09 16:57 ` Richard Purdie
2017-12-09 17:17 ` Richard Purdie [this message]
2017-12-18 15:16 ` Maxin B. John
2017-12-12 13:17 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2018-01-12 12:26 [PATCH] pkgconf: upgrade to 1.4.0 Maxin B. John
2018-01-12 12:26 ` [PATCH] i2c-tools: upgrade to 4.0 Maxin B. John
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=1512839873.19417.120.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=maxin.john@intel.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