From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Miroslav Rezanina <mrezanin@redhat.com>
Subject: Re: [PATCH-for-4.1? 0/7] vl: Allow building with CONFIG_BLUETOOTH disabled
Date: Thu, 7 Nov 2019 20:31:55 +0100 [thread overview]
Message-ID: <831c720f-17b7-c19d-292c-4832b7d8b1b8@redhat.com> (raw)
In-Reply-To: <d79cec06-ff17-a118-7bf9-91ae1791c014@redhat.com>
On 07/11/2019 20.09, Philippe Mathieu-Daudé wrote:
[...]
> Bluetooth is dead, long live BT!
>
> v4.2.0-rc0 just got tagged. We should stop linking unmaintained dead
> code. If nobody step in to nuke BT, we should consider applying this
> series before we release QEMU 5.0 with dead Bluetooth. This approach is
> still better than burying our head in the sand.
FWIW, I'm planning to send some patches to remove the bluetooth code in
the 5.0 development cycle. Unless you want to beat me to it. But I don't
think it makes sense to still make this configurable. The bluetooth code
has been marked as deprecated for a while now, and nobody spoke up that
they are still using it (and as far as I can tell, it's currently not
usable anymore anyway), so it should simply be removed now.
Thomas
prev parent reply other threads:[~2019-11-07 19:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 13:39 [Qemu-devel] [PATCH-for-4.1? 0/7] vl: Allow building with CONFIG_BLUETOOTH disabled Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 1/7] hw/arm: Nokia N-series tablet requires Bluetooth Philippe Mathieu-Daudé
2019-07-15 13:05 ` Thomas Huth
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1 2/7] hw/usb: Bluetooth HCI USB depends on USB & BLUETOOTH Philippe Mathieu-Daudé
2019-07-12 13:58 ` Paolo Bonzini
2019-07-12 14:16 ` Philippe Mathieu-Daudé
2019-07-12 14:58 ` Paolo Bonzini
2019-07-12 16:45 ` Philippe Mathieu-Daudé
2019-07-12 17:31 ` Paolo Bonzini
2019-07-14 16:01 ` Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 3/7] MAINTAINERS: Add an entry for the Bluetooth devices Philippe Mathieu-Daudé
2019-08-14 12:47 ` Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 4/7] vl: Fix 'braces' coding style issues Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 5/7] vl: Use qemu_strtoi() instead of strtol() Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 6/7] vl: Extract bt_parse() into its own file Philippe Mathieu-Daudé
2019-07-12 13:39 ` [Qemu-devel] [PATCH-for-4.1? 7/7] hw/bt: Allow building with CONFIG_BLUETOOTH disabled Philippe Mathieu-Daudé
2019-07-15 13:08 ` Thomas Huth
2019-07-14 11:04 ` [Qemu-devel] [PATCH-for-4.1? 0/7] vl: " Richard Henderson
2019-07-15 13:13 ` Thomas Huth
2019-08-13 14:00 ` Philippe Mathieu-Daudé
2019-08-13 14:04 ` Peter Maydell
2019-08-14 12:45 ` Philippe Mathieu-Daudé
2019-11-07 19:09 ` Philippe Mathieu-Daudé
2019-11-07 19:31 ` Thomas Huth [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=831c720f-17b7-c19d-292c-4832b7d8b1b8@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=mrezanin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).