Re: Lack of review from Renesas

[Wolfram Sang <wsa+renesas@sang-engineering.com>]

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

Hi Krzysztof,

adding some relevant people...

> What just happened - sending a patch to fix in-flight (not applied)
> patch instead of just reviewing it [1] - is not acceptable. You should
> work together, review each other patches and improve them BEFORE they
> got merged.

Did this happen multiple times now? Or was it the first time? I agree it
should be avoided.

> Why? Because you put unnecessary load on maintainers, you allow
> knowingly incomplete or buggy or inefficient patches to get in, you do
> not collaborate in open source.

The opposite is true. There is not just "Renesas". Renesas has multiple
divisions, and as you surely know, within bigger companies it can be
complicated to work together internally, think of a division in Europe
and one in Japan. So, the connection point for these divisions is
actually the public lists. We do this development *in the open*. And,
yes, sometimes shit happens.

> And I really do not care about your patch count

Wrong assumption. Nobody here cares about patch count, we want to
support hardware, that's all.

> If this is how @renesas.com submissions work, I will stop trusting them
> and assume your patches are unreviewed internally and buggy.

I told you more than once that it is perfectly fine for us if you skip
reviews until peolpe you trust (e.g. Geert or me) have reviewed them.
Why don't you just do it?

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]