From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Parthiban Nallathambi <parthiban@linumiz.com>
Cc: marcin@bis.org.pl, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] bluez5_utils: disable asha profile
Date: Sat, 14 Sep 2024 15:16:09 +0200 [thread overview]
Message-ID: <20240914151609.520c70e7@windsurf> (raw)
In-Reply-To: <20240914125406.3026002-1-parthiban@linumiz.com>
Hello Parthiban,
On Sat, 14 Sep 2024 18:24:05 +0530
Parthiban Nallathambi <parthiban@linumiz.com> wrote:
> asha profile as it depends on audio profile which isn't selected
> by default (BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_AUDIO), results in
> below linking failure.
>
> ld: profiles/audio/bluetoothd-asha.o: in function `get_transport':
> asha.c:(.text.get_transport+0x2c): undefined reference to `media_transport_get_path'
>
> Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com>
Thanks for the patch! I believe it's fixing an autobuilder failure,
isn't it? If that's the case, then we like to have:
Fixes:
http://autobuild.buildroot.net/results/75cd510e55d50a1a2da6e9e285ec7a09201d854a/
in the commit message. Of course the reference above is a random build
failure. Could you provide that information? I don't think you really
need to send a new iteration of this patch, just provide a reference to
the autobuilder build failure. But for next patches, you will know it's
something we like to have :-)
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-14 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 12:54 [Buildroot] [PATCH] bluez5_utils: disable asha profile Parthiban Nallathambi
2024-09-14 13:16 ` Thomas Petazzoni via buildroot [this message]
2024-09-14 14:00 ` Parthiban
2024-09-14 14:11 ` Yann E. MORIN
2024-09-23 18:51 ` Yann E. MORIN
2024-10-03 17:00 ` James Hilliard
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=20240914151609.520c70e7@windsurf \
--to=buildroot@buildroot.org \
--cc=marcin@bis.org.pl \
--cc=parthiban@linumiz.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox