[PATCH v4 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes

[George Moussalem]

On 3/14/25 12:23, Krzysztof Kozlowski wrote:
> On Fri, Mar 14, 2025 at 09:56:43AM +0400, George Moussalem wrote:
>> +			msi-map = <0x0 &v2m0 0x0 0xff8>;
>> +
>> +			interrupts = <GIC_SPI 111 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 112 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 113 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 115 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 117 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH>,
>> +				     <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH>;
> 
> Was this tested?
> 
> Anyway, your patchset cannot be even applied due to broken threading.
> 
> We keep pointing to issues in your toolset since more than a week.
> Sending is so trivial that I do not understand why you keep it having
> broken:
> 
> `b4 send`
> or
> `git format-patch -v4 --cover-letter -6 && git send-email ./v4-*`
> 
> NAK

Not disagreeing, but I'm not sure why it still breaks.

The git send-email command is exactly what I used before but I found out 
it's not an issue in the toolset itself. Outlook.com SMTP servers 
replace the original 'Message-ID' header with their own. That is what 
causes threading to break. As a workaround, I first send the cover 
letter, lookup the Message-ID value and then send the actual patches 
using 'git send-email --in-reply-to=<Message-ID>'. I do see them 
threaded in my mail client (Thunderbird) and in:
https://lore.kernel.org/all/DS7PR19MB8883F2538AA7D047E13C102B9DD22@DS7PR19MB8883.namprd19.prod.outlook.com/#r

If this doesn't work, I may need to switch to a different email address.

> 
> Best regards,
> Krzysztof
> 

Best regards,
George