public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Emil Velikov via B4 Relay <devnull+emil.l.velikov.gmail.com@kernel.org>
Cc: linux-bluetooth@vger.kernel.org, emil.velikov@collabora.com
Subject: Re: [PATCH BlueZ 00/10] Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service
Date: Tue, 16 Jan 2024 19:02:19 +0000	[thread overview]
Message-ID: <170543173952.30188.12996299112617772130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240116-autofoo-v1-0-626f6b54bd06@gmail.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 16 Jan 2024 13:51:54 +0000 you wrote:
> Hello everyone,
> 
> While looking at our bluez package for the SteamDeck a handful of
> paper cuts stood out. Here we tackle the build related ones - a couple
> more series will be incoming shortly.
> 
> In a gist we have the following:
>  - remove manual tracking of .services.in, DEPENDENCIES
>  - remove unused variables
>  - polish PKG_CHECK_MODULES handling
>  - enable linker garbage collection
>  - create a symlink to dbus-org.bluez.obex.service
> 
> [...]

Here is the summary with links:
  - [BlueZ,01/10] build: remove unused AM_CONDITIONAL
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6d6294036c39
  - [BlueZ,02/10] build: tweak PKG_CHECK_MODULES calls
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c07fb1fcddad
  - [BlueZ,03/10] build: require libudev 196, circa 2012
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3f490a69cb55
  - [BlueZ,04/10] build: remove dummy {conf,state}{dir,_DATA}
    (no matching commit)
  - [BlueZ,05/10] build: remove unused variable builtin_nodist
    (no matching commit)
  - [BlueZ,06/10] build: remove .service files from DEPENDENCIES lists
    (no matching commit)
  - [BlueZ,07/10] build: remove explicit DEPENDENCIES handling
    (no matching commit)
  - [BlueZ,08/10] build: manage .service.in files via configure.ac
    (no matching commit)
  - [BlueZ,09/10] build: enable gc/dead code removal
    (no matching commit)
  - [BlueZ,10/10] build: install dbus-org.bluez.obex.service symlink
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-16 19:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 13:51 [PATCH BlueZ 00/10] Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service Emil Velikov via B4 Relay
2024-01-16 13:51 ` [PATCH BlueZ 01/10] build: remove unused AM_CONDITIONAL Emil Velikov via B4 Relay
2024-01-16 15:41   ` Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service bluez.test.bot
2024-01-16 13:51 ` [PATCH BlueZ 02/10] build: tweak PKG_CHECK_MODULES calls Emil Velikov via B4 Relay
2024-01-16 13:51 ` [PATCH BlueZ 03/10] build: require libudev 196, circa 2012 Emil Velikov via B4 Relay
2024-01-16 13:51 ` [PATCH BlueZ 04/10] build: remove dummy {conf,state}{dir,_DATA} Emil Velikov via B4 Relay
2024-01-16 18:40   ` Luiz Augusto von Dentz
2024-01-17  8:39     ` Emil Velikov
2024-01-18 16:12       ` Emil Velikov
2024-01-18 17:05         ` Luiz Augusto von Dentz
2024-01-19 11:09           ` Emil Velikov
2024-01-19 15:09             ` Luiz Augusto von Dentz
2024-01-16 13:51 ` [PATCH BlueZ 05/10] build: remove unused variable builtin_nodist Emil Velikov via B4 Relay
2024-01-16 13:52 ` [PATCH BlueZ 06/10] build: remove .service files from DEPENDENCIES lists Emil Velikov via B4 Relay
2024-01-16 13:52 ` [PATCH BlueZ 07/10] build: remove explicit DEPENDENCIES handling Emil Velikov via B4 Relay
2024-01-16 13:52 ` [PATCH BlueZ 08/10] build: manage .service.in files via configure.ac Emil Velikov via B4 Relay
2024-01-16 13:52 ` [PATCH BlueZ 09/10] build: enable gc/dead code removal Emil Velikov via B4 Relay
2024-01-16 13:52 ` [PATCH BlueZ 10/10] build: install dbus-org.bluez.obex.service symlink Emil Velikov via B4 Relay
2024-01-16 19:02 ` patchwork-bot+bluetooth [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=170543173952.30188.12996299112617772130.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=devnull+emil.l.velikov.gmail.com@kernel.org \
    --cc=emil.velikov@collabora.com \
    --cc=linux-bluetooth@vger.kernel.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