Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Seonggon Cho <jmsmg1@me.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] mpris-proxy: Line-buffer stdout
Date: Wed, 30 Sep 2026 15:40:08 +0000	[thread overview]
Message-ID: <179078280827.1986714.14953752400407137061.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929024530.3978095-1-jmsmg1@me.com>

Hello:

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

On Tue, 29 Sep 2026 02:45:30 +0000 you wrote:
> mpris-proxy reports adapter and player changes with printf() but never
> flushes stdout. When it runs as a service (tools/mpris-proxy.service)
> stdout is a pipe to the journal, so glibc fully buffers it and nothing
> is written until 4 KiB have accumulated or the process exits.
> 
> On a system whose Bluetooth adapter went away and came back every two
> minutes, the "Bluetooth Adapter /org/bluez/hci0 removed" and "... found"
> messages reached the journal in bursts of exactly 100 lines (about
> 4096 bytes), all carrying the timestamp of the flush rather than of the
> event, i.e. up to about 80 minutes late.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] mpris-proxy: Line-buffer stdout
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a086d234e503

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



      parent reply	other threads:[~2026-09-30 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  0:34 [PATCH BlueZ] mpris-proxy: Line-buffer stdout Seonggon Cho
2026-09-29  2:12 ` [BlueZ] " bluez.test.bot
2026-09-29  2:45 ` [PATCH BlueZ v2] " Seonggon Cho
2026-09-29  7:56   ` [BlueZ,v2] " bluez.test.bot
2026-09-30 15: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=179078280827.1986714.14953752400407137061.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=jmsmg1@me.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