From: "Sinan Kaya" <okaya@kernel.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH v5] net-tools: split mii-tool into its own package
Date: Mon, 4 Jan 2021 11:08:45 -0500 [thread overview]
Message-ID: <c3d2d85c-cc9d-d60f-6f5b-1068104c13bd@kernel.org> (raw)
In-Reply-To: <036d635c9ab0f70b30df61bc65a53ce32de2f13e.camel@linuxfoundation.org>
On 12/22/2020 4:51 AM, Richard Purdie wrote:
> I'm still trying to work through testing of these. This one seems to
> result in:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/3077/steps/11/logs/warnings
>
> which is from net-tools-native.
>
> NETTOOLS_PACKAGES_class-native = ""
>
> may be the neatest fix for that I can think of offhand.
Thanks for taking care of this.
prev parent reply other threads:[~2021-01-04 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 22:48 [meta-oe][PATCH v5] net-tools: split mii-tool into its own package Sinan Kaya
2020-12-22 9:51 ` [OE-core] " Richard Purdie
2021-01-04 16:08 ` Sinan Kaya [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=c3d2d85c-cc9d-d60f-6f5b-1068104c13bd@kernel.org \
--to=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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