linux-kernel - Re: [PATCH V2 0/1] arm64: dts: qcom: qcs8300-ride: Enable Bluetooth support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a25bd3e4-95c8-47ed-8b2e-93c168283205@oss.qualcomm.com>
Date: Tue, 18 Nov 2025 15:20:01 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Wei Deng <wei.deng@....qualcomm.com>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
        cheng.jiang@....qualcomm.com, quic_jiaymao@...cinc.com,
        quic_chezhou@...cinc.com, quic_shuaz@...cinc.com
Subject: Re: [PATCH V2 0/1] arm64: dts: qcom: qcs8300-ride: Enable Bluetooth
 support

On 11/18/25 3:04 PM, Wei Deng wrote:
> Changes for v2
> - Update commit message, add firmware name detail
> - Reorganize patchset
> - V1 link
>   https://lore.kernel.org/all/20251113130942.2661069-1-wei.deng@oss.qualcomm.com/
> 
> Wei Deng (1):
>   arm64: dts: qcom: qcs8300-ride: Enable Bluetooth support
> 
>  arch/arm64/boot/dts/qcom/qcs8300-ride.dts | 28 +++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> 
> base-commit: e7c375b181600caf135cfd03eadbc45eb530f2cb
> prerequisite-patch-id: babbcf9dd8722e19d91b01eb45756f58e58ba6ac
> prerequisite-patch-id: e641f09d4139ac77c34757bd08af2db746de3963
> prerequisite-patch-id: f5dd3ee9979e2a049badfb51cfab184da4501870
> prerequisite-patch-id: 40187dae2c9518a10866104b9fcd5a481ac67d51
> prerequisite-patch-id: b9a2e071f5ddcc70dbd6addcbf738afdc9283cdc

Sorry, this screams "unmergeable". If you have more than one or two
predictably-soon-to-be-merged dependencies, you should instead wait
for those to be resolved. You can help in that by testing and helping
to review them.

prerequisite-patch-id also doesn't even tell us what these patches
really are.. prerequisite-message-id is probably better

Konrad