From: Seonggon Cho <jmsmg1@me.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] mpris-proxy: Line-buffer stdout
Date: Tue, 29 Sep 2026 02:46:25 +0000 [thread overview]
Message-ID: <20260929024625.3978431-1-jmsmg1@me.com> (raw)
In-Reply-To: <20260929024302.3977246-1-jmsmg1@me.com>
This is an accidental duplicate of
https://lore.kernel.org/linux-bluetooth/20260929003432.3937487-1-jmsmg1@me.com/
(re-ran the wrong command). Please ignore this copy; v2 with the
checkpatch fix is in the original thread.
next prev parent reply other threads:[~2026-09-29 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 2:43 [PATCH BlueZ] mpris-proxy: Line-buffer stdout Seonggon Cho
2026-09-29 2:46 ` Seonggon Cho [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-29 0:34 Seonggon Cho
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=20260929024625.3978431-1-jmsmg1@me.com \
--to=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