From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <Ross.Burton@arm.com>, Yoann Congal <yoann.congal@smile.fr>
Cc: Khem Raj <raj.khem@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>,
Tim Orling <ticotimo@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [OE-core] [PATCH v3] strace: Disable bluetooth support by default
Date: Fri, 15 Dec 2023 12:24:05 +0000 [thread overview]
Message-ID: <3dc045e3b2ef9099dd85da35469053ad0384ce54.camel@linuxfoundation.org> (raw)
In-Reply-To: <4F557F6F-8492-4027-AD2C-97773A476624@arm.com>
On Fri, 2023-12-15 at 11:59 +0000, Ross Burton wrote:
> On 15 Dec 2023, at 10:49, Yoann Congal <yoann.congal@smile.fr> wrote:
> > FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-
> > raid tests) also prevent bluez to be built in a default core-image-
> > minimal build, we can skip this one (strace: Disable bluetooth
> > support by default) and still fix [YOCTO #15323].
>
> I’m a fan of both. Bluetooth support in strace is a niche usecase and easily enabled.
I have a half drafted email saying I was thinking of both too! (I then
got distracted).
Cheers,
Richard
next prev parent reply other threads:[~2023-12-15 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 8:56 [PATCH v3] strace: Disable bluetooth support by default Yoann Congal
2023-12-14 9:09 ` [OE-core] " Alexander Kanavin
2023-12-14 9:50 ` Richard Purdie
2023-12-14 12:03 ` Alexander Kanavin
2023-12-14 12:11 ` Richard Purdie
2023-12-14 12:17 ` Alexander Kanavin
2023-12-14 12:30 ` Richard Purdie
2023-12-14 12:34 ` Alexander Kanavin
2023-12-14 12:37 ` Richard Purdie
2023-12-14 13:02 ` Jose Quaresma
2023-12-14 18:29 ` Khem Raj
2023-12-14 18:53 ` Khem Raj
2023-12-14 19:33 ` Alexandre Belloni
2023-12-14 19:36 ` Khem Raj
2023-12-15 10:49 ` Yoann Congal
2023-12-15 11:59 ` Ross Burton
2023-12-15 12:24 ` Richard Purdie [this message]
2023-12-14 13:23 ` Richard Purdie
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=3dc045e3b2ef9099dd85da35469053ad0384ce54.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ticotimo@gmail.com \
--cc=yoann.congal@smile.fr \
/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.