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: <fef8569d-0172-48a6-b2cb-0e9023589ced@kernel.org>
Date: Fri, 7 Nov 2025 08:04:31 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Xuyang Dong <dongxuyang@...incomputing.com>, mturquette@...libre.com,
 sboyd@...nel.org, robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 bmasney@...hat.com, troy.mitchell@...ux.spacemit.com,
 linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Cc: ningyu@...incomputing.com, linmin@...incomputing.com,
 huangyifeng@...incomputing.com, pinkesh.vaghela@...fochips.com
Subject: Re: [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock
 controller

On 07/11/2025 07:20, Xuyang Dong wrote:
>>>
>>>   Gentle ping. Looking forward to your reply. Thank you very much!
>>
>> Please do not top post.
>>
>> You did not add any maintainers of these drivers, so I would not put it
>> high on our priority list.  Ask yourself - why would community
>> maintainer like to take unmaintained driver? So the community maintainer
>> would maintain, right? To add him more work? If that is the case, isn't
>> better not to take the driver? You see where I am getting at?
>>
>> Also, I don't see any involvement in reviews from eswin. The only
>> reviews here where from DT maintainers, Troy and Brian (I hope I did not
>> miss anyone), so again - you just put all the effort on us and then ping
>> us...
>>
> 
> Hello Krzysztof Brian Troy,
> 
> Would you kindly review the updated v7 patches at your earliest convenience?
> 
> Thanks to Krzysztof for your reply.
> 
> These patches have already undergone review within our internal team. 
> The reason for adding eswin maintainers to the mailing list is to ensure 
> that these colleagues can promptly receive community feedback and stay 
> informed of the discussions.

Please really, really think through my first paragraph. It seems you did
not get the point, but understanding the point is essential for all your
future (and this) upstreaming efforts.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ