From: Breno Leitao <leitao@debian.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: net: convert remaining bluetooth socket families to getsockopt_iter
Date: Mon, 11 May 2026 05:29:08 -0700 [thread overview]
Message-ID: <agHLeMrI_ua1yKIs@gmail.com> (raw)
In-Reply-To: <6a01b70b.050a0220.366c6d.5746@mx.google.com>
On Mon, May 11, 2026 at 04:01:31AM -0700, bluez.test.bot@gmail.com wrote:
> This is an automated email and please do not reply to this email.
>
> Dear Submitter,
>
> Thank you for submitting the patches to the linux bluetooth mailing list.
> While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
What is the HEAD of the repository? This should apply against
linux-next-alike branch.
next prev parent reply other threads:[~2026-05-11 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 10:41 [PATCH net-next 0/7] net: convert remaining bluetooth socket families to getsockopt_iter Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 1/7] Bluetooth: hci_sock: write the full optval for getsockopt Breno Leitao
2026-05-11 11:01 ` net: convert remaining bluetooth socket families to getsockopt_iter bluez.test.bot
2026-05-11 12:29 ` Breno Leitao [this message]
2026-05-11 10:41 ` [PATCH net-next 2/7] Bluetooth: hci_sock: convert " Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 3/7] Bluetooth: ISO: " Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 4/7] Bluetooth: RFCOMM: " Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 5/7] Bluetooth: L2CAP: " Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 6/7] selftests: net: getsockopt_iter: cover SCO BT_CODEC conversion Breno Leitao
2026-05-11 13:47 ` Jakub Kicinski
2026-05-11 14:19 ` Breno Leitao
2026-05-11 10:41 ` [PATCH net-next 7/7] Bluetooth: SCO: convert to getsockopt_iter Breno Leitao
2026-05-12 17:50 ` [PATCH net-next 0/7] net: convert remaining bluetooth socket families " 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=agHLeMrI_ua1yKIs@gmail.com \
--to=leitao@debian.org \
--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