All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Michael Nosthoff <buildroot@heine.tech>, buildroot@buildroot.org
Cc: Marcin Bis <marcin@bis.org.pl>
Subject: Re: [Buildroot] [PATCH] package/bluez5_utils: hid2hci needs tools
Date: Tue, 3 Aug 2021 23:25:19 +0200	[thread overview]
Message-ID: <7cee3c4d-2b54-6c33-1dd6-5e0aad1b3aea@mind.be> (raw)
In-Reply-To: <20210803123330.70319-1-buildroot@heine.tech>



On 03/08/2021 14:33, Michael Nosthoff via buildroot wrote:
> fixes:
> http://autobuild.buildroot.net/results/9f91d530c22cad053d89a7bf54c4567d3012d05e
> http://autobuild.buildroot.net/results/80b90e1b6fee99ed7bf4aed87a14311a12469993
> http://autobuild.buildroot.net/results/444eaab22b140b26a730c7fdd4bada71a8d6fef2
> 
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>

 Applied to master, thanks.

 Regards,
 Arnout

> ---
>  package/bluez5_utils/Config.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/bluez5_utils/Config.in b/package/bluez5_utils/Config.in
> index a8232279bd..2eea8c7ced 100644
> --- a/package/bluez5_utils/Config.in
> +++ b/package/bluez5_utils/Config.in
> @@ -143,6 +143,7 @@ config BR2_PACKAGE_BLUEZ5_UTILS_TOOLS_HID2HCI
>  	bool "build hid2hci tool"
>  	depends on BR2_PACKAGE_HAS_UDEV
>  	select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_HID # runtime
> +	select BR2_PACKAGE_BLUEZ5_UTILS_TOOLS
>  	help
>  	  Build hid2hci tool
>  
> 
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-08-04  1:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 12:33 [Buildroot] [PATCH] package/bluez5_utils: hid2hci needs tools Michael Nosthoff via buildroot
2021-08-03 21:25 ` Arnout Vandecappelle [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=7cee3c4d-2b54-6c33-1dd6-5e0aad1b3aea@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=buildroot@heine.tech \
    --cc=marcin@bis.org.pl \
    /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.