All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kirill Samburskiy <k.samburskiy@omp.ru>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/1] obexd: Fix transfer status change
Date: Wed, 26 Nov 2025 16:40:05 +0000	[thread overview]
Message-ID: <176417520550.1757232.14120803150904739540.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125093835.17472-1-k.samburskiy@omp.ru>

Hello:

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

On Tue, 25 Nov 2025 12:38:34 +0300 you wrote:
> See the issue for details: https://github.com/bluez/bluez/issues/1683
> 
> Kirill Samburskiy (1):
>   obexd: Always flush tranfser status changes. Set status to queued
>     before starting
> 
>  obexd/plugins/opp.c | 2 ++
>  obexd/src/manager.c | 9 ++++++++-
>  obexd/src/manager.h | 1 +
>  3 files changed, 11 insertions(+), 1 deletion(-)

Here is the summary with links:
  - [BlueZ,1/1] obexd: Always flush tranfser status changes. Set status to queued before starting
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d4218235678c

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



      parent reply	other threads:[~2025-11-26 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  9:38 [PATCH BlueZ 0/1] obexd: Fix transfer status change Kirill Samburskiy
2025-11-25  9:38 ` [PATCH BlueZ 1/1] obexd: Always flush tranfser status changes. Set status to queued before starting Kirill Samburskiy
2025-11-25 10:35   ` obexd: Fix transfer status change bluez.test.bot
2025-11-26 16:40 ` 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=176417520550.1757232.14120803150904739540.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=k.samburskiy@omp.ru \
    --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.