All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,1/3] doc/qualification: Add PICS and howto for the BAP qualification
Date: Fri, 18 Sep 2026 07:03:09 -0700 (PDT)	[thread overview]
Message-ID: <6aad449d.b41fd234.46d10.7f66@mx.google.com> (raw)
In-Reply-To: <20260903085716.741578-1-frederic.danis@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 715 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:       [BlueZ,1/3] doc/qualification: Add PICS and howto for the BAP qualification
   Pull Request: https://github.com/bluez/bluez/pull/2477
   Created:      2026-09-03 11:12:57+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

  parent reply	other threads:[~2026-09-18 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  8:57 [PATCH BlueZ 1/3] doc/qualification: Add PICS and howto for the BAP qualification Frédéric Danis
2026-09-03  8:57 ` [PATCH BlueZ 2/3] doc/qualification: Add BAP/UCL tests Frédéric Danis
2026-09-03  8:57 ` [PATCH BlueZ 3/3] doc/qualification: Add BAP/USR tests Frédéric Danis
2026-09-03 11:53 ` [BlueZ,1/3] doc/qualification: Add PICS and howto for the BAP qualification bluez.test.bot
2026-09-18 14:03 ` bluez.test.bot [this message]
2026-09-28 20:10 ` [PATCH BlueZ 1/3] " patchwork-bot+bluetooth

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=6aad449d.b41fd234.46d10.7f66@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=frederic.danis@collabora.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.