All of lore.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 v2 0/6] Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service
Date: Thu, 25 Jan 2024 19:10:27 +0000	[thread overview]
Message-ID: <170620982787.23941.6481888174452761774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240124-autofoo-v2-0-a210f20aa2f7@gmail.com>

Hello:

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

On Wed, 24 Jan 2024 16:20:05 +0000 you wrote:
> Hello everyone,
> 
> Here is v2 of the autotoo papercuts.
> 
> Changes in this revision:
>  - dropped already merged patches - thanks o/
>  - drop "build: remove dummy {conf,state}{dir,_DATA}" patch
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/6] build: remove unused variable builtin_nodist
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=215e6c7083da
  - [BlueZ,v2,2/6] build: remove .service files from DEPENDENCIES lists
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=14c7f21292b1
  - [BlueZ,v2,3/6] build: remove explicit DEPENDENCIES handling
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=808d008aace3
  - [BlueZ,v2,4/6] build: manage .service.in files via configure.ac
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=116524c01de4
  - [BlueZ,v2,5/6] build: enable gc/dead code removal
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=10d6d908b5fe
  - [BlueZ,v2,6/6] build: install dbus-org.bluez.obex.service symlink
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1cd6c874c271

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-25 19:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 16:20 [PATCH BlueZ v2 0/6] Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service Emil Velikov
2024-01-24 16:20 ` Emil Velikov via B4 Relay
2024-01-24 16:20 ` [PATCH BlueZ v2 1/6] build: remove unused variable builtin_nodist Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-24 18:33   ` Autotools papercuts, linker GC, symlink dbus-org.bluez.obex.service bluez.test.bot
2024-01-24 16:20 ` [PATCH BlueZ v2 2/6] build: remove .service files from DEPENDENCIES lists Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-24 16:20 ` [PATCH BlueZ v2 3/6] build: remove explicit DEPENDENCIES handling Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-24 16:20 ` [PATCH BlueZ v2 4/6] build: manage .service.in files via configure.ac Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-24 16:20 ` [PATCH BlueZ v2 5/6] build: enable gc/dead code removal Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-24 16:20 ` [PATCH BlueZ v2 6/6] build: install dbus-org.bluez.obex.service symlink Emil Velikov
2024-01-24 16:20   ` Emil Velikov via B4 Relay
2024-01-25 19:10 ` 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=170620982787.23941.6481888174452761774.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 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.