From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org
Subject: [BlueZ] Pull Request #2469 was closed: input: retry HOG GATT reads on ATT Unlikely Error (0x0E)
Date: Wed, 16 Sep 2026 23:43:32 -0700 (PDT) [thread overview]
Message-ID: <6aab8c14.53afd7a3.307036.28dc@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
This is an automated email and please do not reply to this email.
The following pull request was open for more than 2 weeks in the BlueZ
Github repository and it was closed automatically without taking any action.
Pull Request: #2469
Title: input: retry HOG GATT reads on ATT Unlikely Error (0x0E)
Submitter: monperrus
Created: 2026-09-02 05:11:52+00:00
URL: https://github.com/bluez/bluez/pull/2469
Note that the BlueZ repo in Github is only for CI and testing purposes and
it doesn't accept any pull request. The patches should be sent to the Linux
Bluetooth mailing list (linux-bluetooth@vger.kernel.org) for review.
If the change should still be considered, it must be resent as a patch to
the Linux Bluetooth mailing list (linux-bluetooth@vger.kernel.org). Closing
the pull request doesn't submit anything on the submitter's behalf and no
further action is taken on it.
---
Regards,
Linux Bluetooth
reply other threads:[~2026-09-17 6:43 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=6aab8c14.53afd7a3.307036.28dc@mx.google.com \
--to=bluez.test.bot@gmail.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