[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BF391DAD-7E2C-44C2-9BE7-C1F7A2946575@kernel.org>
Date: Tue, 13 May 2025 17:41:15 +0200
From: Niklas Cassel <cassel@...nel.org>
To: Hans Zhang <18255117159@....com>,
Krzysztof Wilczyński <kw@...ux.com>
CC: lpieralisi@...nel.org, bhelgaas@...gle.com, jingoohan1@...il.com,
manivannan.sadhasivam@...aro.org, robh@...nel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v2 0/3] Standardize link status check to return bool
On 13 May 2025 17:09:58 CEST, Hans Zhang <18255117159@....com> wrote:
>
>
>On 2025/5/13 23:04, Krzysztof Wilczyński wrote:
>> Hello,
>>
>> [...]
>>> Sorry, this is also the first time I have done this. For other patches in
>>> the future, I will do this in the new version.
>>
>> See the following:
>>
>> - https://lore.kernel.org/linux-pci/20250513145728.GA3513600@rocinante
>>
>> While I cannot speak for other maintainers, I am going to change the
>> approach to the "RESEND" patches that I used to personally have.
>>
>> But, if in doubt, it's always fine to send another version.
>>
>
>
>Dear Krzysztof,
>
>Ok. From now on, I will handle similar problems in the new version.
While I agree that it is always fine to send a new revision (which has picked up tags),
having the RESEND tag is gently informing that the series might have fell thorough the cracks.
This information might be lost/less obvious if simply sending a new revision (assuming that commit log and code is unchanged).
Kind regards,
Niklas
Powered by blists - more mailing lists