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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 5 Feb 2024 09:33:14 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Anjelique Melendez <quic_amelende@...cinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, lee@...nel.org, 
	robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, 
	agross@...nel.org, konrad.dybcio@...aro.org, linux-leds@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
	linux-pwm@...r.kernel.org
Subject: Re: Re: [PATCH 1/2] dt-bindings: soc: qcom: Add qcom,pbs bindings

On Fri, Feb 02, 2024 at 09:49:21AM -0800, Anjelique Melendez wrote:
> 
> 
> On 2/1/2024 11:29 PM, Krzysztof Kozlowski wrote:
> > On 01/02/2024 21:44, Anjelique Melendez wrote:
> >> Add binding for the Qualcomm Programmable Boot Sequencer device.
> >>
> >> Signed-off-by: Anjelique Melendez <quic_amelende@...cinc.com>
> >> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> > 
> > How is it possible? This is v1, not a resend, and I never give review
> > tags not in public.
> > 
> > Best regards,
> > Krzysztof
> > 
> Sorry for the confusion, this patch was originally in this series:
> https://lore.kernel.org/all/20231221185838.28440-2-quic_amelende@quicinc.com/,
> where you gave your reviewed by tag in v3:
> https://lore.kernel.org/all/102328fa-5699-4731-d639-079bce8863a5@linaro.org/.
> This was separated into a new series since half of the original
> patches were already applied. I mentioned this in the cover
> letter but in future should I keep version the same as the original
> series?
> 

Marking the patch(es) v9 makes it clear that they have been on the list
already. This would be true either if you rebased v8 (and git dropped
the applied patches from your series), or if you resubmitted some patch
on it's own.

Regards,
Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ