From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 01/17] connman-conf: ignore eth0 in qemu in a way that is not sysvinit-specific
Date: Wed, 20 Apr 2022 22:00:42 +0100 [thread overview]
Message-ID: <c309ea4f1d7e0b777fdc789ad2ccef5b35f80ffa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdYwkknc5MT69Ze1=uN48YFbzf3U8kTGpBCvk1k-G50Ujw@mail.gmail.com>
On Wed, 2022-04-20 at 10:05 -1000, Steve Sakoman wrote:
> I still occasionally get the ping error on dunfell autobuilder runs,
> so I suspect it needs something similar to this patch.
>
> I'm not conman literate, so if someone who is can create a patch for
> dunfell I would be most appreciative! The recipe differences between
> master and dunfell are great enough that I don't trust myself :-)
Also note that this did require meta-agl to make changes to their layer to adapt
to what core did...
Cheers,
Richard
prev parent reply other threads:[~2022-04-21 16:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 17:00 [PATCH 01/17] connman-conf: ignore eth0 in qemu in a way that is not sysvinit-specific Alexander Kanavin
2022-04-07 17:00 ` [PATCH 02/17] llvm: update 13.0.1 -> 14.0.0 Alexander Kanavin
2022-04-08 7:03 ` [OE-core] " Richard Purdie
2022-04-08 8:12 ` Alexander Kanavin
2022-04-07 17:00 ` [PATCH 03/17] llvm: use default install paths Alexander Kanavin
2022-04-07 17:00 ` [PATCH 04/17] squashfs-tools: update 4.5 -> 4.5.1 Alexander Kanavin
2022-04-07 19:55 ` [OE-core] " Khem Raj
2022-04-07 19:59 ` Alexander Kanavin
2022-04-07 20:04 ` Khem Raj
2022-04-07 17:00 ` [PATCH 05/17] go-helloworld: update to latest revision Alexander Kanavin
2022-04-07 17:00 ` [PATCH 06/17] piglit: " Alexander Kanavin
2022-04-07 17:00 ` [PATCH 07/17] vulkan-samples: " Alexander Kanavin
2022-04-07 17:00 ` [PATCH 08/17] libxvmc: update 1.0.12 -> 1.0.13 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 09/17] libsndfile1: update 1.0.31 -> 1.1.0 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 10/17] at-spi2-core: update 2.42.0 -> 2.44.0 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 11/17] webkitgtk: update 2.34.6 -> 2.36.0 Alexander Kanavin
2022-04-09 3:25 ` [OE-core] " Khem Raj
2022-04-07 17:00 ` [PATCH 12/17] cmake: update 3.22.3 -> 3.23.0 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 13/17] epiphany: upgrade 41.3 -> 42.0 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 14/17] gdk-pixbuf: upgrade 2.42.6 -> 2.42.8 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 15/17] libgcrypt: upgrade 1.9.4 -> 1.10.1 Alexander Kanavin
2022-04-07 19:46 ` [OE-core] " Khem Raj
2022-04-07 19:56 ` Alexander Kanavin
2022-04-07 17:00 ` [PATCH 16/17] librsvg: upgrade 2.52.7 -> 2.54.0 Alexander Kanavin
2022-04-07 17:00 ` [PATCH 17/17] python3-typing-extensions: upgrade 3.10.0.0 -> 4.1.1 Alexander Kanavin
2022-04-07 19:43 ` [OE-core] " Khem Raj
2022-04-07 19:45 ` Alexander Kanavin
2022-04-07 19:59 ` Khem Raj
2022-04-07 21:14 ` Richard Purdie
2022-04-20 20:05 ` [OE-core] [PATCH 01/17] connman-conf: ignore eth0 in qemu in a way that is not sysvinit-specific Steve Sakoman
2022-04-20 21:00 ` 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=c309ea4f1d7e0b777fdc789ad2ccef5b35f80ffa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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 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.