From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Changhyeok Bae <changhyeok.bae@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] iproute2: Upgrade 4.10.0 -> 4.11.0
Date: Sun, 11 Jun 2017 23:06:00 +0100 [thread overview]
Message-ID: <1497218760.3942.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <1496899587-30479-1-git-send-email-changhyeok.bae@gmail.com>
On Thu, 2017-06-08 at 05:26 +0000, Changhyeok Bae wrote:
> Signed-off-by: Changhyeok Bae <changhyeok.bae@gmail.com>
> ---
> .../iproute2/{iproute2_4.10.0.bb =>
> iproute2_4.11.0.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-connectivity/iproute2/{iproute2_4.10.0.bb =>
> iproute2_4.11.0.bb} (75%)
Failed to build with musl:
https://autobuilder.yocto.io/builders/nightly-musl/builds/297/steps/BuildImages/logs/stdio
Cheers,
Richard
prev parent reply other threads:[~2017-06-11 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 5:26 [PATCH] iproute2: Upgrade 4.10.0 -> 4.11.0 Changhyeok Bae
2017-06-11 22:06 ` Richard Purdie [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=1497218760.3942.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=changhyeok.bae@gmail.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