[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <655c2b73-4ecf-4201-83b8-bbddfd68027e@linux.dev>
Date: Wed, 18 Dec 2024 11:24:06 +0800
From: Sui Jingfeng <sui.jingfeng@...ux.dev>
To: Shuah <shuah@...nel.org>, Xi Ruoyao <xry111@...111.site>,
WANG Xuerui <kernel@...0n.name>, Icenowy Zheng <uwu@...nowy.me>,
Huacai Chen <chenhuacai@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"Mike Rapoport (IBM)" <rppt@...nel.org>, Baoquan He <bhe@...hat.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
David Hildenbrand <david@...hat.com>, Zhen Lei <thunder.leizhen@...wei.com>,
Thomas Gleixner <tglx@...utronix.de>, Zhihong Dong <donmor3000@...mail.com>,
loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org,
"conduct@...nel.org" <conduct@...nel.org>
Subject: Re: [PATCH v2] loongarch/mm: disable WUC for pgprot_writecombine as
same as ioremap_wc
Hi,
On 2024/12/18 02:18, Shuah wrote:
> On 12/2/24 09:23, Sui Jingfeng wrote:
>> Hi,
>>
>
>>> IIUC this is a hardware bug of 7A1000 and 7A2000, so the proper
>>> location
>>> of the workaround is in the bridge chip driver. Or am I
>>> misunderstanding something?
>>>
>>
>> You are misunderstanding everything and ranting like a dog.
>>
>
> Sui Jingfeng,
>
> This is not the way to work with your fellow developers in the
> community to express disagreements.
I'm not expressing disagreements, but argue that the contributor
and/or talker should provide *sufficient* hardware details and
tests. Instead of pointless *ranting* in order to get harmful
patch merged.
The discussion completely not make scene at all.
> I would recommend following up with an apology.
>
I will not apology to indecent contributors and/or maintainers
like this, never.
> thanks,
> -- Shuah
>
>
>
>
>
--
Best regards,
Sui
Powered by blists - more mailing lists