On Sat, Apr 27, 2024 at 01:57:46PM +0800, Sui Jingfeng wrote:
Hi,You should seriously consider your tone when replying then.
On 2024/4/26 14:23, Maxime Ripard wrote:
Hi,No one is preventing you, as long as don't misunderstanding what other
On Fri, Apr 26, 2024 at 04:43:18AM +0800, Sui Jingfeng wrote:
On 2024/4/26 03:10, Andy Shevchenko wrote:Most of the interactions you had in this series has been uncalled for.
On Fri, Apr 26, 2024 at 02:08:16AM +0800, Sui Jingfeng wrote:I'm actually a professional display drivers developer at the downstream
On 2024/4/25 22:26, Andy Shevchenko wrote:Huh?! Really, stop commenting the stuff you do not understand.
It seems driver missed the point of proper use of device property APIs.You are using the 'seems' here exactly saying that you are not 100% sure.
Correct this by updating headers and calls respectively.
Please allow me to tell you the truth: This patch again has ZERO effect.
It fix nothing. And this patch is has the risks to be wrong.
in the past, despite my contribution to upstream is less. But I believe
that all panel driver developers know what I'm talking about. So please
have take a look at my replies.
You might be against a patch, but there's no need to go to such length.
As far as I'm concerned, this patch is fine to me in itself, and I don't
see anything that would prevent us from merging it.
people's technical replies intentionally. I'm just a usual and normal
contributor, I hope the world will better than yesterday.
Saying such thing to me may not proper, I guess you may want to talkI think you misunderstood me. My point was that your several rants were
to peoples who has the push rights
uncalled for and aren't the kind of things we're doing here.
I know very well how to get a patch merged, thanks.
just make sure it isn't a insult to the professionalism of drm bridgeI'm not sure why you're bringing the bridge community or its
community itself though.
professionalism. It's a panel, not a bridge, and I never doubted the
professionalism of anyone.
Maxime