From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] df891f: sco-tester: Fix closing the socket
Date: Wed, 12 Mar 2025 07:41:29 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/95055d-adcd73@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: df891f0ff44e0d67c4e60bd6f9e03b89a316164e
https://github.com/bluez/bluez/commit/df891f0ff44e0d67c4e60bd6f9e03b89a316164e
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-03-11 (Tue, 11 Mar 2025)
Changed paths:
M tools/sco-tester.c
Log Message:
-----------
sco-tester: Fix closing the socket
When writting data the socket shall not be closed until all the data
could be transmitted or the test times out.
Commit: adcd73901831c0a4e2469ab3705608745af259f6
https://github.com/bluez/bluez/commit/adcd73901831c0a4e2469ab3705608745af259f6
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-03-11 (Tue, 11 Mar 2025)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
btdev: Fix double lookup
This fixes the existing double lookup when calling
num_completed_packets but passing the conn->handle instead of passing
the conn pointer directly since num_completed_packets would then attempt
to do another lookup by handle to resolve the conn pointer again.
Compare: https://github.com/bluez/bluez/compare/95055def8cd2...adcd73901831
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-03-12 14:41 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/95055d-adcd73@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 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.