All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Lang Daniel via buildroot <buildroot@buildroot.org>
Cc: Lang Daniel <d.lang@abatec.at>, "marcin@bis.org.pl" <marcin@bis.org.pl>
Subject: Re: [Buildroot] [PATCH 1/2] package/bluez5_utils: fix media control profile
Date: Sun, 19 Mar 2023 14:51:11 +0100	[thread overview]
Message-ID: <20230319145111.6bacfd53@windsurf> (raw)
In-Reply-To: <VI1P190MB049389FDF2EA1D1EAB8292B99FBC9@VI1P190MB0493.EURP190.PROD.OUTLOOK.COM>

On Thu, 16 Mar 2023 13:53:04 +0000
Lang Daniel via buildroot <buildroot@buildroot.org> wrote:

> With bluez 5.66 (bumped in c6c79d6) the Media Control Profile (MCP), Basic
> Audio Profile (BAP) and Volume Control Profile (VCP) where added.
> All three are enabled by default.
> MCP only works if AVRCP is enabled, as it requires player.c which is
> otherwise not compiled.
> Only enable all three new profiles when the audio plugin is selected.
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/d62/d6260a5acf766657f683d85fa1bdc27b7a43551e/
> 
> Signed-off-by: Daniel Lang <d.lang@abatec.at>
> ---
>  package/bluez5_utils/bluez5_utils.mk | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-03-19 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 13:53 [Buildroot] [PATCH 1/2] package/bluez5_utils: fix media control profile Lang Daniel via buildroot
2023-03-19 13:51 ` Thomas Petazzoni via buildroot [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=20230319145111.6bacfd53@windsurf \
    --to=buildroot@buildroot.org \
    --cc=d.lang@abatec.at \
    --cc=marcin@bis.org.pl \
    --cc=thomas.petazzoni@bootlin.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.