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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAfSe-uHuoBBKkSU-pDaNVYNCrfgqjh07gX7jS6uvO3AQF7b-g@mail.gmail.com>
Date: Thu, 21 Nov 2024 11:04:33 +0800
From: Chunyan Zhang <zhang.lyra@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Baolin Wang <baolin.wang@...ux.alibaba.com>, 
	Stanislav Jakubek <stano.jakubek@...il.com>, robh@...nel.org, conor+dt@...nel.org, 
	devicetree@...r.kernel.org, krzk+dt@...nel.org, linux-kernel@...r.kernel.org, 
	orsonzhai@...il.com, Cixi Geng <cixi.geng@...ux.dev>
Subject: Re: [PATCH] arm64: dts: sprd: Remove unused and undocumented
 "constant_charge_voltage_max_microvolt" property

Hi Krzysztof,

On Wed, 20 Nov 2024 at 22:25, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>
> On 20/11/2024 13:27, Baolin Wang wrote:
> >
> >
> > On 2024/11/20 20:14, Stanislav Jakubek wrote:
> >> Hi Rob,
> >>
> >> constant-charge-voltage-max-microvolt is a valid property, which I assume
> >> was the original intention here. I've already submitted a patch changing this
> >> to the documented property:
> >>
> >> https://lore.kernel.org/lkml/aa557091d9494fdaa3eda75803f9ea97014c8832.1730918663.git.stano.jakubek@gmail.com/
> >>
> >> Baolin also reviewed that patch... make of that what you will.
> >
> > Ah, yes. Sorry I forgot your patch. Thanks for reminding.
>
> No one picked them up... I kept Stanislav's patches in my incoming/inbox
> folder for quite long time, because I pick up some random fixes here and
> there, but then forgot them and did not apply for v6.13-rc1. So they
> missed v6.13-rc1.
>
> I am not the maintainer of that platform, so I don't care about it
> really, but I care about contributors work not being lost/ignored.
>
> What is the plan with these and all other Spreadtrum patches? Are they
> going to be applied by you or other Spreadtrum maintainers? Do you need
> any help from us? Or maybe some clarifications of the process?

Yes we need your help!

The Spreadtrum DTS patches had been being maintained through my tree.
I'm not suitable to do this any more due to some changes (I've moved
myself to the reviewer entry of sprd).

After discussion with other sprd maintainers, we still want the
Spreadtrum patches to go through your tree if you agree.

Thanks for all the help,
Chunyan

>
> Best regards,
> Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ