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: <992d46b7-b053-4a9e-ba04-f5653525a891@kernel.org>
Date: Tue, 2 Dec 2025 16:59:30 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Hrishabh Rajput <hrishabh.rajput@....qualcomm.com>,
 Bjorn Andersson <andersson@...nel.org>, Guenter Roeck <linux@...ck-us.net>,
 Wim Van Sebroeck <wim@...ux-watchdog.org>
Cc: linux-arm-msm@...r.kernel.org, linux-watchdog@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 Pavan Kondeti <pavan.kondeti@....qualcomm.com>,
 Neil Armstrong <neil.armstrong@...aro.org>,
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
 Shivendra Pratap <shivendra.pratap@....qualcomm.com>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH v8 0/2] Add support for Gunyah Watchdog

On 02/12/2025 12:23, Hrishabh Rajput wrote:
> Hi Bjorn, Guenter, and Wim,
> 
> Just a gentle ping on this series.

It's merge window. There was no point in pinging just before merge
window and is even worse to ping now. Nothing can happen with this
patchset and such pings is only noise.

> 
> Since the patches have received Reviewed-by tags from Dmitry and 
> Guenter, I wanted to confirm the merge strategy.
> 
> Bjorn: Are you planning to pick the QCOM SCM changes separately through 
> your tree, or would you prefer the whole series go through the Watchdog 
> tree?
> If the latter, do we need an explicit Acked-by from you for QCOM SCM patch?

Where did you document dependencies between patches and any non-obvious
merging? I open cover letter and there is NOTHING. I look at patch
changelog and also NOTHING.

So if you tell us nothing, why would we care to think we need to do
anything special here?

You must explicitly document every dependency, both external and between
patches, in the cover letter. At least cover letter, some people (e.g.
mostly me) don't even read them...

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ