From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: Initial support for GATT Proxy Service
Date: Fri, 11 Jul 2025 11:16:05 -0700 (PDT) [thread overview]
Message-ID: <687154e5.050a0220.132d0.a713@mx.google.com> (raw)
In-Reply-To: <20250711175842.28860-2-ceggers@arri.de>
[-- Attachment #1: Type: text/plain, Size: 635 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 -----
.git/rebase-apply/patch:395: trailing whitespace.
.git/rebase-apply/patch:395: new blank line at EOF.
+
error: patch failed: mesh/net.c:192
error: mesh/net.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:[~2025-07-11 18:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 14:22 [RFC PATCH BlueZ 0/4] Initial support for GATT Proxy Service Christian Eggers
2025-07-01 14:22 ` [RFC PATCH BlueZ 1/4] mesh: acceptor: increase interval for unprovisioned device beacon Christian Eggers
2025-07-01 16:02 ` Initial support for GATT Proxy Service bluez.test.bot
2025-07-01 14:22 ` [RFC PATCH BlueZ 2/4] mesh: add support for provisioning via GATT Christian Eggers
2025-07-01 14:22 ` [RFC PATCH BlueZ 3/4] mesh: add GATT proxy service Christian Eggers
[not found] ` <CABUQxGwt8MjoYmx_8jF=A9qug24Dnx+rEX=5vDWP7+SGOERcMw@mail.gmail.com>
2025-07-01 19:28 ` Christian Eggers
2025-07-01 14:22 ` [RFC PATCH BlueZ 4/4] mesh: initial support for proxy configuration messages via GATT Christian Eggers
2025-07-01 15:09 ` [RFC PATCH BlueZ 0/4] Initial support for GATT Proxy Service Christian Eggers
2025-07-01 16:07 ` Luiz Augusto von Dentz
2025-07-01 16:38 ` Christian Eggers
2025-07-01 19:11 ` Luiz Augusto von Dentz
2025-07-01 19:17 ` Brian Gix
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 0/7] " Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 1/7] mesh: acceptor: increase interval for unprovisioned device beacon Christian Eggers
2025-07-11 18:16 ` bluez.test.bot [this message]
2025-07-15 15:56 ` Initial support for GATT Proxy Service bluez.test.bot
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 2/7] mesh: add support for provisioning via GATT Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 3/7] mesh: add GATT proxy service Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 4/7] mesh: gatt-proxy: support for proxy configuration messages and filtering Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 5/7] mesh: main.conf/cfgmod-server: allow to enable proxy support Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 6/7] mesh: net: proxy relaying Christian Eggers
2025-07-11 17:56 ` [RFC PATCH BlueZ v2 7/7] mesh: gatt-proxy: propagate beacons Christian Eggers
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=687154e5.050a0220.132d0.a713@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ceggers@arri.de \
--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