[v2] arm64: dts: qcom: qcs8300-ride: Enable Bluetooth support

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

Posted by Wei Deng 1 week, 6 days ago

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
-- 
2.25.1

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

Posted by Krzysztof Kozlowski 1 week, 6 days ago

On 18/11/2025 15:04, 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


Nothing improved. Please look at your git history BEFORE you start
sending code.

Best regards,
Krzysztof

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

Posted by Konrad Dybcio 1 week, 6 days ago

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