linux-kernel - Re: [PATCH v3 0/6] Enable IPQ5018 PCI 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] [day] [month] [year] [list]

Message-ID:
 <DS7PR19MB8883932996C1C2BBD84249BD9DCB2@DS7PR19MB8883.namprd19.prod.outlook.com>
Date: Wed, 5 Mar 2025 21:54:47 +0400
From: George Moussalem <george.moussalem@...look.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, linux-arm-msm@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
 linux-phy@...ts.infradead.org, andersson@...nel.org, bhelgaas@...gle.com,
 conor+dt@...nel.org, devicetree@...r.kernel.org,
 dmitry.baryshkov@...aro.org, kishon@...nel.org, konradybcio@...nel.org,
 krzk+dt@...nel.org, kw@...ux.com, lpieralisi@...nel.org,
 manivannan.sadhasivam@...aro.org, p.zabel@...gutronix.de,
 quic_nsekar@...cinc.com, robh@...nel.org, robimarko@...il.com,
 vkoul@...nel.org
Cc: quic_srichara@...cinc.com
Subject: Re: [PATCH v3 0/6] Enable IPQ5018 PCI support



On 3/5/25 20:47, Krzysztof Kozlowski wrote:
> On 05/03/2025 14:41, George Moussalem wrote:
>> From: Sricharan Ramabadhran <quic_srichara@...cinc.com>
>>
>> This patch series adds the relevant phy and controller
>> DT configurations for enabling PCI gen2 support
>> on IPQ5018. IPQ5018 has two phys and two controllers, 
>> one dual-lane and one single-lane.
>>
>> Last patch series (v2) submitted dates back to August 27, 2024.
>> As I've worked to add IPQ5018 platform support in OpenWrt, I'm
>> continuing the efforts to add Linux kernel support.
> Why is this changelog separate? We talked about this 5 revisions ago and
> you keep doing the same mistakes.
I've finally figured it out. It wasn't a git send-email bug I was running into.
I just analyzed the entire mail flow and found Outlook.com smtp servers replace the Message-ID
header value with the server name handling the email and places the actual Message-ID in another attribute
called X-Microsoft-Original-Message-ID. So when send-email sets the In-Reply-To header,
it uses the right one but the outlook.com mail servers replaced it with another value so threading breaks.

As a workaround, which I just tested, I will send the cover letter separately first, pick up the value
of Message-ID (which isn't the original one), and send the remaining patches with the --in-reply-to
argument of git send-email set to the newly replaced Message-ID.

This works. And apologies for the confusion/mess.
>
> Best regards,
> Krzysztof
Best regards,
George