From: patchwork-bot+ofono@kernel.org
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH] bluez4: Remove support
Date: Sat, 06 Apr 2024 20:30:25 +0000 [thread overview]
Message-ID: <171243542544.22154.6383468636929866789.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240406195550.2950800-1-denkenz@gmail.com>
Hello:
This patch was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Sat, 6 Apr 2024 14:55:35 -0500 you wrote:
> BlueZ 5 is now up to release 5.73, with the 5.0 release date being in
> late 2012. There's very little chance that anyone is using BlueZ 4
> anymore. Remove it.
> ---
> Makefile.am | 32 +-
> btio/btio.c | 1447 ---------------------------------------
> btio/btio.h | 110 ---
> configure.ac | 1 -
> dundee/bluez4.c | 296 --------
> plugins/bluez4.c | 988 --------------------------
> plugins/bluez4.h | 84 ---
> plugins/dun_gw_bluez4.c | 172 -----
> plugins/hfp_ag_bluez4.c | 218 ------
> plugins/hfp_hf_bluez4.c | 554 ---------------
> plugins/sap.c | 363 ----------
> 11 files changed, 1 insertion(+), 4264 deletions(-)
> delete mode 100644 btio/btio.c
> delete mode 100644 btio/btio.h
> delete mode 100644 dundee/bluez4.c
> delete mode 100644 plugins/bluez4.c
> delete mode 100644 plugins/bluez4.h
> delete mode 100644 plugins/dun_gw_bluez4.c
> delete mode 100644 plugins/hfp_ag_bluez4.c
> delete mode 100644 plugins/hfp_hf_bluez4.c
> delete mode 100644 plugins/sap.c
Here is the summary with links:
- bluez4: Remove support
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=6bd9bd2c9efa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-06 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 19:55 [PATCH] bluez4: Remove support Denis Kenzior
2024-04-06 20:30 ` patchwork-bot+ofono [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=171243542544.22154.6383468636929866789.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=denkenz@gmail.com \
--cc=ofono@lists.linux.dev \
/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