From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] mpris-proxy: Add mpris:artUrl support
Date: Tue, 04 Feb 2025 22:50:36 +0000 [thread overview]
Message-ID: <173870943624.172153.7815659979300581943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250204154020.95539-1-frederic.danis@collabora.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 4 Feb 2025 16:40:18 +0100 you wrote:
> This commit connects to the bip-avrcp Obex service if the
> org.bluez.MediaPlayer ObexPort property exists.
> Once connected, the Track properties update may contain an
> ImgHandle which is automatically downloaded, then a Metadata
> property updated signal is sent on org.mpris.MediaPlayer2.Player
> interface.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] mpris-proxy: Add mpris:artUrl support
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=01a5a268143e
- [BlueZ,v2,2/2] mpris-proxy: Fix infinite list items reception
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4bc8660651f4
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:[~2025-02-04 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 15:40 [PATCH BlueZ v2 1/2] mpris-proxy: Add mpris:artUrl support Frédéric Danis
2025-02-04 15:40 ` [PATCH BlueZ v2 2/2] mpris-proxy: Fix infinite list items reception Frédéric Danis
2025-02-04 17:13 ` [BlueZ,v2,1/2] mpris-proxy: Add mpris:artUrl support bluez.test.bot
2025-02-04 22:50 ` 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=173870943624.172153.7815659979300581943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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.