linux-kernel - Re: [PATCH v5? 0/6] Tweaked basic Synopsys DW HDMI QP TX driver for Rockchip RK3588

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: <440c8b2b-035b-4983-b078-78252a17725d@collabora.com>
Date: Fri, 30 Aug 2024 22:51:23 +0300
From: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
To: Shimrra Shai <shimrrashai@...il.com>
Cc: Laurent.pinchart@...asonboard.com, aarnoud@...com, airlied@...il.com,
 algea.cao@...k-chips.com, andrzej.hajda@...el.com, andy.yan@...k-chips.com,
 conor+dt@...nel.org, daniel@...ll.ch, devicetree@...r.kernel.org,
 dri-devel@...ts.freedesktop.org, heiko@...ech.de, hjc@...k-chips.com,
 jernej.skrabec@...il.com, jonas@...boo.se, krzk+dt@...nel.org,
 ldearquer@...il.com, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
 maarten.lankhorst@...ux.intel.com, markyao0591@...il.com,
 mripard@...nel.org, neil.armstrong@...aro.org, rfoss@...nel.org,
 robh@...nel.org, s.hauer@...gutronix.de, tzimmermann@...e.de
Subject: Re: [PATCH v5? 0/6] Tweaked basic Synopsys DW HDMI QP TX driver for
 Rockchip RK3588

Hi Shimrra,

On 8/30/24 8:54 PM, Shimrra Shai wrote:
> Cristian Ciocaltea wrote:
>> Please stop doing this!
>>
>> I appreciate your intention to help, but this is not the proper way of
>> doing it.  This is a work-in-progress series and you should have asked
>> before taking over.  Please do not interfere with other people's work
>> without having a preliminary agreement with the author(s).
>>
>> Additionally, before submitting any other patches, you should get
>> familiar with the process - see [1] for a starting point.
>>
> 
> Hi Cristian,
> 
> Sorry, I did not know what the rules/norms/customs were around this
> kind of thing here as I figured it was an open contribution space. I
> did not know that I should have asked for agreement with you
> beforehand. So go ahead and ignore this patch series if it goes
> against the rules/customs. Even more if these points have already been
> addressed, as redundant work is obviously not helpful.

This is an open community and, obviously, anyone is free to contribute
without asking for permission.  However, taking over an ongoing work is
nothing but a source of confusion.  You may do this for work that is known
to be abandoned, e.g. the author(s) explicitly mentioned that in one of
their last posts, or when there is no sign of activity for long enough
time (usually months, for sure not days or weeks).  In the latter case, I
find it reasonable to still ask for a confirmation that the submitter has
no intention to continue or, at least, discuss the possibilities to join
forces and help moving further.

> That said, if there is some way to help along this project "the right
> way", I would like to for sure! Just tell me what you'd _really_ need
> help/assistance with to get this moved ahead and I'll see if I can
> give it.

Getting more testing on the series, reporting back the findings and/or
providing fixes, would be much appreciated, for sure!  The goal is to land
the basic functionality first, hence any new features should be submitted
afterwards.

Regards,
Cristian