Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/uclibc: Enable wordexp functionality
Date: Tue, 21 Mar 2017 20:53:26 +0100	[thread overview]
Message-ID: <20170321195326.GE28589@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170321160237.31058-2-andriy.shevchenko@linux.intel.com>

Hi,
Andy Shevchenko wrote,

> The commit d7c54cb0c0cf ("bluez5_utils: not available with uClibc")
> disables bluez5_utils (most of them) to be built with uClibc. Looking to
> the development of BlueZ user space support that commit basically makes
> the bluez5_utils package somewhat piece of junk. Since bluez5_utils 5.44
> deprecates all previously used tools and focuses on btmgmt and
> bluetoothctl we need to restore status quo.

You can add my Acked-By. It will allow to use more applications and
I think it is just a minor size increase.

Looking forward to your size comparison requested by Thomas,

Thanks
 Waldemar

  parent reply	other threads:[~2017-03-21 19:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 16:02 [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Andy Shevchenko
2017-03-21 16:02 ` [Buildroot] [PATCH v2] package/uclibc: Enable wordexp functionality Andy Shevchenko
2017-03-21 16:06   ` Thomas Petazzoni
2017-03-21 16:11     ` Andy Shevchenko
2017-03-21 16:17       ` Thomas Petazzoni
2017-03-21 16:23         ` Andy Shevchenko
2017-03-21 16:28       ` Baruch Siach
2017-04-09  4:32     ` Waldemar Brodkorb
2017-04-09  7:42       ` Thomas Petazzoni
2017-03-21 19:53   ` Waldemar Brodkorb [this message]
2017-04-16 14:29   ` Waldemar Brodkorb
2017-04-29 12:26   ` Thomas Petazzoni
2017-03-21 16:02 ` [Buildroot] [PATCH v2] Revert "bluez5_utils: not available with uClibc" Andy Shevchenko
2017-03-21 17:01 ` [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Peter Korsgaard
2017-03-21 17:06   ` Andy Shevchenko

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=20170321195326.GE28589@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@busybox.net \
    /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