From: Dmitry Baryshkov <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e73bf5: shared/shell: Don't init input for non-interactive...
Date: Wed, 07 Jan 2026 18:55:28 +0000 (UTC) [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/b35b6b-38ac68@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e73bf582dae60356641a32fc27ae03d359ec4c47
https://github.com/bluez/bluez/commit/e73bf582dae60356641a32fc27ae03d359ec4c47
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Date: 2026-01-07 (Wed, 07 Jan 2026)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: Don't init input for non-interactive shells
Only the interactive shell is supposed to read comments from the input
file descriptor. Rework bt_attach_shell() in order to stop calling
input_new() / io_new() in a non-interactive case.
Fixes: https://github.com/bluez/bluez/issues/700
Commit: 38ac68e239090f01eb39511921a703667266c310
https://github.com/bluez/bluez/commit/38ac68e239090f01eb39511921a703667266c310
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Date: 2026-01-07 (Wed, 07 Jan 2026)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: make bt_attach_shell more obvious
There are only two cases, interactive and non-interactive. Make that
more obvious by using if-else rather than two if-checks.
Compare: https://github.com/bluez/bluez/compare/b35b6befb12c...38ac68e23909
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-01-07 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/b35b6b-38ac68@github.com \
--to=noreply@github.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