All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Yauhen Kharuzhy <yauhen.kharuzhy@softeq.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] shared/mcp: Implement next/previous track commands
Date: Wed, 19 Jun 2024 14:10:29 +0000	[thread overview]
Message-ID: <171880622911.19669.9913507880334963530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240619120433.3666313-1-yauhen.kharuzhy@softeq.com>

Hello:

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

On Wed, 19 Jun 2024 15:04:32 +0300 you wrote:
> Add bt_mcp_{next,previous}_track functions to shared MCP client
> profile code. This allows user to have basic control of the media player
> in addition to simple play/pause/stop actions.
> ---
>  src/shared/mcp.c | 20 ++++++++++++++++++++
>  src/shared/mcp.h |  2 ++
>  2 files changed, 22 insertions(+)

Here is the summary with links:
  - [BlueZ,v2,1/2] shared/mcp: Implement next/previous track commands
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a91471400f97
  - [BlueZ,v2,2/2] mcp: Implement Next Track and Previous Track commands
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=811e48d340d8

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:04 [PATCH BlueZ v2 1/2] shared/mcp: Implement next/previous track commands Yauhen Kharuzhy
2024-06-19 12:04 ` [PATCH BlueZ v2 2/2] mcp: Implement Next Track and Previous Track commands Yauhen Kharuzhy
2024-06-19 14:10 ` patchwork-bot+bluetooth [this message]
2024-06-19 14:23 ` [BlueZ,v2,1/2] shared/mcp: Implement next/previous track commands bluez.test.bot

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=171880622911.19669.9913507880334963530.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yauhen.kharuzhy@softeq.com \
    /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.