All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ooonea@gmail.com
Subject: RE: None
Date: Sat, 10 Oct 2026 18:20:01 -0700 (PDT)	[thread overview]
Message-ID: <6acae441.bdce4de1.160bb7.6f5d@mx.google.com> (raw)
In-Reply-To: <CACmoRBYCiLYXr05CLjvAA4wPpbjje2BhFHe1v9fEfSFAWFR89w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

This is an automated email and please do not reply to this email.

Dear Submitter,

This series was picked up by the CI more than 2 weeks ago and the pull
request created for it is still open, which means the series was never
applied to the tree.

   Series:       None
   Pull Request: https://github.com/bluez/bluez/pull/2593
   Created:      2026-09-26 00:38:20+00:00

The pull request has been closed and no further action is taken on this
series.

If the change should still be considered, it must be resent to the Linux
Bluetooth mailing list (linux-bluetooth@vger.kernel.org) so that it is
picked up again.

---
Regards,
Linux Bluetooth

  reply	other threads:[~2026-10-11  1:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 17:42 [PATCH BlueZ 1/2] input: Reset report map state on detach Giuseppe Piscitelli
2026-09-25 17:43 ` [PATCH BlueZ 2/2] unit: Test HoG report map reads after reconnect Giuseppe Piscitelli
2026-09-25 20:05 ` [BlueZ,1/2] input: Reset report map state on detach bluez.test.bot
2026-09-25 22:03 ` [PATCH BlueZ v2 1/2] " Giuseppe Piscitelli
2026-09-26  1:30   ` [BlueZ,v2,1/2] " bluez.test.bot
2026-10-11  1:20   ` bluez.test.bot
2026-09-25 22:03 ` [PATCH BlueZ v2 2/2] unit: Test HoG report map reads after reconnect Giuseppe Piscitelli
2026-10-11  1:20   ` bluez.test.bot [this message]
2026-09-28 17:48 ` [PATCH BlueZ 1/2] input: Reset report map state on detach Luiz Augusto von Dentz
2026-09-28 21:03   ` Giuseppe Piscitelli
2026-10-10 19:23 ` [BlueZ,1/2] " bluez.test.bot
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16 18:43 Dorcas Litunya
2023-10-17 20:21 ` none Junio C Hamano
2019-11-20  3:49 Han-Wen Nienhuys
2019-11-20  4:52 ` none Junio C Hamano
2019-11-20  5:00   ` none Han-Wen Nienhuys
2019-03-03 13:20 [PATCH 1/3] test functions: Add new function `test_file_not_empty` Junio C Hamano
2019-03-03 13:29 ` Rohit Ashiwal
2019-03-03 13:33   ` none Junio C Hamano
2018-10-05  6:20 [PATCH] doc: fix a typo and clarify a sentence Junio C Hamano
2018-10-10 15:20 ` Mihir Mehta
2018-10-10 22:19   ` none Junio C Hamano
2016-04-11 19:04 (unknown), miwilliams
2016-04-11 19:18 ` none Matthieu Moy
2014-08-29 14:22 No subject Ravi Raj
2014-08-29 14:47 ` Valdis.Kletnieks at vt.edu
2014-08-29 14:58   ` Ravi Raj
2014-08-29 15:32     ` No subject Valdis.Kletnieks at vt.edu
2014-08-29 15:53       ` none Bjørn Mork
2009-07-01  3:37 Larry Finger
2009-07-01  8:32 ` none Kalle Valo
2009-07-01  3:36 Larry Finger
2009-07-01  8:31 ` none Kalle Valo
2005-05-19  6:23 none Gerald Turner
2003-08-28 19:08 none kartikey bhatt
2003-06-30 16:11 None 
2003-06-19 11:45 None Владимир Сорокин
2002-07-17 14:19 None Bloch, Jack
2002-07-17 14:15 None irfan_hamid
2000-11-16 10:03 Sergey Volkoff
2000-11-16 14:46 ` none Chmouel Boudjnah
1997-05-27 13:36 root
1999-04-07 15:09 ` none Eric W. Biederman

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=6acae441.bdce4de1.160bb7.6f5d@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ooonea@gmail.com \
    /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.