From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_chejiang@quicinc.com
Subject: RE: Expand firmware-name property to load specific
Date: Thu, 05 Dec 2024 02:46:16 -0800 (PST) [thread overview]
Message-ID: <67518478.170a0220.de6f7.272e@mx.google.com> (raw)
In-Reply-To: <20241205102213.1281865-2-quic_chejiang@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 586 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: arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi:857
error: arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi: 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-12-05 10:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 10:22 [PATCH v3 0/3] Expand firmware-name property to load specific Cheng Jiang
2024-12-05 10:22 ` [PATCH v3 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-05 10:46 ` bluez.test.bot [this message]
2024-12-05 11:18 ` Rob Herring (Arm)
2024-12-06 3:06 ` Cheng Jiang (IOE)
2024-12-05 14:36 ` Krzysztof Kozlowski
2024-12-06 3:05 ` Cheng Jiang (IOE)
2024-12-05 10:22 ` [PATCH v3 2/3] Bluetooth: qca: Expand firmware-name to load specific nvm and rampatch Cheng Jiang
2024-12-05 12:00 ` Dmitry Baryshkov
2024-12-06 3:05 ` Cheng Jiang (IOE)
2024-12-06 8:34 ` Dmitry Baryshkov
2024-12-09 9:03 ` Cheng Jiang (IOE)
2024-12-09 10:49 ` Dmitry Baryshkov
2024-12-09 13:59 ` Cheng Jiang (IOE)
2024-12-09 16:04 ` Dmitry Baryshkov
2024-12-10 2:00 ` Cheng Jiang (IOE)
2024-12-10 11:12 ` Dmitry Baryshkov
2024-12-10 15:03 ` Cheng Jiang (IOE)
2024-12-05 14:02 ` kernel test robot
2024-12-05 14:37 ` Krzysztof Kozlowski
2024-12-06 2:42 ` Cheng Jiang (IOE)
2024-12-05 10:22 ` [PATCH v3 3/3] arm64: dts: qcom: sa8775p-ride: Add firmware-name in BT node Cheng Jiang
2024-12-05 12:13 ` Dmitry Baryshkov
2024-12-06 2:39 ` Cheng Jiang (IOE)
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 15:16 [PATCH v4 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-10 15:45 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-12 15:02 [PATCH v5 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-12 15:17 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-17 14:24 [PATCH v6 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-17 15:00 ` Expand firmware-name property to load specific bluez.test.bot
2025-01-07 9:26 [PATCH v6 RESEND 1/3] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2025-01-07 9:56 ` Expand firmware-name property to load specific 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=67518478.170a0220.de6f7.272e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_chejiang@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).