All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1] client/player: Fix printing errors when transport->filename is not set
Date: Thu, 18 Jul 2024 18:30:35 +0000	[thread overview]
Message-ID: <172132743581.20188.10635080064564115676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240718180059.1159551-2-luiz.dentz@gmail.com>

Hello:

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

On Thu, 18 Jul 2024 14:00:59 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> If transport->filename is not set don't attempt to write to the
> transport->fd.
> ---
>  client/player.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Here is the summary with links:
  - [BlueZ,v1] client/player: Fix printing errors when transport->filename is not set
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=957c956112cc

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



  reply	other threads:[~2024-07-18 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 18:00 [PATCH BlueZ v1] client/player: Add support for name custom presets Luiz Augusto von Dentz
2024-07-18 18:00 ` [PATCH BlueZ v1] client/player: Fix printing errors when transport->filename is not set Luiz Augusto von Dentz
2024-07-18 18:30   ` patchwork-bot+bluetooth [this message]
2024-07-18 19:46   ` [BlueZ,v1] " bluez.test.bot
2024-07-18 18:30 ` [PATCH BlueZ v1] client/player: Add support for name custom presets patchwork-bot+bluetooth
2024-07-18 19:45 ` [BlueZ,v1] " 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=172132743581.20188.10635080064564115676.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.