From: Adrian Bunk <bunk@stusta.de>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Remove remnants of bluez4 support
Date: Sat, 13 Jul 2019 09:53:23 +0300 [thread overview]
Message-ID: <20190713065323.GA21584@localhost> (raw)
In-Reply-To: <20190712075547.GA1468@jama>
On Fri, Jul 12, 2019 at 09:55:47AM +0200, Martin Jansa wrote:
> On Fri, Jul 12, 2019 at 10:48:13AM +0300, Adrian Bunk wrote:
>...
> > --- a/meta/conf/distro/include/default-providers.inc
> > +++ b/meta/conf/distro/include/default-providers.inc
> > @@ -44,7 +44,7 @@ PREFERRED_PROVIDER_nativesdk-opkg ?= "nativesdk-opkg"
> > PREFERRED_PROVIDER_console-tools ?= "kbd"
> > PREFERRED_PROVIDER_gzip-native ?= "pigz-native"
> > PREFERRED_PROVIDER_udev ?= "${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd','eudev',d)}"
> > -PREFERRED_RPROVIDER_bluez-hcidump ?= "${@bb.utils.contains('DISTRO_FEATURES','bluetooth bluez5','bluez5','bluez-hcidump',d)}"
> > +PREFERRED_RPROVIDER_bluez-hcidump ?= "${@bb.utils.contains('DISTRO_FEATURES','bluetooth','bluez5','bluez-hcidump',d)}"
>
> Is this still needed?
>
> With all remnants of bluez4 gone, bluez-hcidump is probably rprovided
> only by bluez5 now.
>...
Thanks, v2 sent.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-07-13 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 7:48 [PATCH] Remove remnants of bluez4 support Adrian Bunk
2019-07-12 7:55 ` Martin Jansa
2019-07-13 6:53 ` Adrian Bunk [this message]
2019-07-12 8:01 ` ✗ patchtest: failure for " Patchwork
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=20190713065323.GA21584@localhost \
--to=bunk@stusta.de \
--cc=martin.jansa@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