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, Joakim.Tjernlund@infinera.com,
emil.l.velikov@gmail.com
Subject: Re: [PATCH BlueZ v2 00/10] Handful of build fixes and cleanups
Date: Tue, 20 Feb 2024 15:00:31 +0000 [thread overview]
Message-ID: <170844123124.11924.8847424394060331888.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240216-hook-fixup-v2-0-a6b192d1a6ad@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 16 Feb 2024 23:11:04 +0000 you wrote:
> Hello list,
>
> Here are bunch of regression fixes caused by yours truly - mea culpa.
>
> Changes in v2:
> - rework first (install-data-hooks) to per-target hooks
> - add renamed files to gitignore (rules patch)
> - introduced six extra patches
> - fix the @@ substitution in the service.in files
> - drop erroneous -fPIC
> - add org.bluez.obex.service to gitignore
> - drop duplicate -I include in obexd
> - adds all manpages to gitignore
> - moves libbluetooth public header to sub-folder
>
> [...]
Here is the summary with links:
- [BlueZ,v2,01/10] build: rework {install-data,uninstall}-hook
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9fe4ccb79ffa
- [BlueZ,v2,02/10] build: install obexd (dbus,systemd} services as needed
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c2b9f357d522
- [BlueZ,v2,03/10] build: handle relative libexecdir instances
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=71d8fda25b21
- [BlueZ,v2,04/10] build: drop %.rules make rule
(no matching commit)
- [BlueZ,v2,05/10] build: simplify coverage handling
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=344cf10cb60c
- [BlueZ,v2,06/10] build: drop explicit -fPIC from obexd CFLAGS
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bade07f43fed
- [BlueZ,v2,07/10] gitignore: add org.bluez.obex.service
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=071ababfe6e3
- [BlueZ,v2,08/10] build: obexd: remove duplicate include -I$(builddir)/lib
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4d3605e472ed
- [BlueZ,v2,09/10] gitignore: ignore all manual pages
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e6acec4770bb
- [BlueZ,v2,10/10] build: move public headers to sub-folder
(no matching commit)
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-02-20 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 23:11 [PATCH BlueZ v2 00/10] Handful of build fixes and cleanups Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 01/10] build: rework {install-data,uninstall}-hook Emil Velikov via B4 Relay
2024-02-17 0:31 ` Handful of build fixes and cleanups bluez.test.bot
2024-02-16 23:11 ` [PATCH BlueZ v2 02/10] build: install obexd (dbus,systemd} services as needed Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 03/10] build: handle relative libexecdir instances Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 04/10] build: drop %.rules make rule Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 05/10] build: simplify coverage handling Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 06/10] build: drop explicit -fPIC from obexd CFLAGS Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 07/10] gitignore: add org.bluez.obex.service Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 08/10] build: obexd: remove duplicate include -I$(builddir)/lib Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 09/10] gitignore: ignore all manual pages Emil Velikov via B4 Relay
2024-02-16 23:11 ` [PATCH BlueZ v2 10/10] build: move public headers to sub-folder Emil Velikov via B4 Relay
2024-02-17 16:09 ` [PATCH BlueZ v2 00/10] Handful of build fixes and cleanups Emil Velikov
2024-02-20 15:00 ` 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=170844123124.11924.8847424394060331888.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=devnull+emil.l.velikov.gmail.com@kernel.org \
--cc=emil.l.velikov@gmail.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;
as well as URLs for NNTP newsgroup(s).