linux-kernel - Re: [PATCH v2 17/21] dt-bindings: serial: document support for SA8255p

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: <156bbd40-bfa6-4b81-bbc6-bdd019a1b585@kernel.org>
Date: Thu, 5 Sep 2024 10:08:16 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Andrew Lunn <andrew@...n.ch>, Nikunj Kela <quic_nkela@...cinc.com>
Cc: andersson@...nel.org, konradybcio@...nel.org, robh@...nel.org,
 krzk+dt@...nel.org, conor+dt@...nel.org, rafael@...nel.org,
 viresh.kumar@...aro.org, herbert@...dor.apana.org.au, davem@...emloft.net,
 sudeep.holla@....com, andi.shyti@...nel.org, tglx@...utronix.de,
 will@...nel.org, robin.murphy@....com, joro@...tes.org,
 jassisinghbrar@...il.com, lee@...nel.org, linus.walleij@...aro.org,
 amitk@...nel.org, thara.gopinath@...il.com, broonie@...nel.org,
 cristian.marussi@....com, rui.zhang@...el.com, lukasz.luba@....com,
 wim@...ux-watchdog.org, linux@...ck-us.net, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-pm@...r.kernel.org, linux-crypto@...r.kernel.org,
 arm-scmi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-i2c@...r.kernel.org, iommu@...ts.linux.dev,
 linux-gpio@...r.kernel.org, linux-serial@...r.kernel.org,
 linux-spi@...r.kernel.org, linux-watchdog@...r.kernel.org,
 kernel@...cinc.com, quic_psodagud@...cinc.com,
 Praveen Talari <quic_ptalari@...cinc.com>
Subject: Re: [PATCH v2 17/21] dt-bindings: serial: document support for
 SA8255p

On 04/09/2024 23:54, Andrew Lunn wrote:
>> No one is born with experience. You learn as you go. Please note that
>> this series has gone through internal review before I posted it in
>> upstream.
> 
> Then i'm surprise you were not told to submit lots of smaller
> patchsets, one per subsystem, which are complete.

We did... multiple times. We gave examples how entire new Qualcomm SoC
should be upstreamed, how this process should be organized. We gave
trainings. Some listen, some not. Sometimes people do not even come to a
training (for free). But there will be always an excuse for patchset
doing something entirely different than community expects...

The patchset here is a result of some misconceptions and not
understanding what is the dependency (claiming there is while there is
no) and what are the maintainer trees.

> 
> I get nobody is born with experience, but for a company the size of
> Qualcomm, they can easily hire a few experienced mainline developers
> who can mentor you, rather than having overloaded Maintainers teach
> you the basics, and getting frustrated in the process.

Best regards,
Krzysztof