From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, surban@surban.net
Subject: RE: [v3] Bluetooth: compute LE flow credits based on recvbuf space
Date: Sun, 07 Apr 2024 18:47:59 -0700 (PDT) [thread overview]
Message-ID: <66134ccf.c80a0220.aa00.01c6@mx.google.com> (raw)
In-Reply-To: <20240408005625.57115-1-surban@surban.net>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
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.
----- Output -----
error: patch failed: include/net/bluetooth/l2cap.h:943
error: include/net/bluetooth/l2cap.h: patch does not apply
error: patch failed: net/bluetooth/l2cap_sock.c:1146
error: net/bluetooth/l2cap_sock.c: patch does not apply
hint: Use 'git am --show-current-patch' to see the failed patch
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-04-08 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 9:38 [PATCH] l2cap: do not return LE flow credits when buf full Sebastian Urban
2024-04-05 10:25 ` [PATCH v2] Bluetooth: keep LE flow credits when recvbuf full Sebastian Urban
2024-04-05 10:56 ` [v2] " bluez.test.bot
2024-04-05 15:30 ` [PATCH v2] " Luiz Augusto von Dentz
2024-04-07 18:57 ` Sebastian Urban
2024-04-05 10:33 ` l2cap: do not return LE flow credits when buf full bluez.test.bot
2024-04-08 0:56 ` [PATCH v3] Bluetooth: compute LE flow credits based on recvbuf space Sebastian Urban
2024-04-08 1:47 ` bluez.test.bot [this message]
2024-04-08 9:41 ` [PATCH v4] " Sebastian Urban
2024-04-08 10:35 ` [v4] " bluez.test.bot
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=66134ccf.c80a0220.aa00.01c6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=surban@surban.net \
/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.