[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2cc391ce-0e87-040f-6a45-d3e128a988f0@huawei.com>
Date: Tue, 18 Jul 2023 16:07:47 +0800
From: "lihuisong (C)" <lihuisong@...wei.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
"xuwei (O)" <xuwei5@...wei.com>
CC: <linux-kernel@...r.kernel.org>, <soc@...nel.org>,
<wanghuiqiang@...wei.com>, <tanxiaofei@...wei.com>,
<liuyonglong@...wei.com>, <andersson@...nel.org>,
<matthias.bgg@...il.com>,
<angelogioacchino.delregno@...labora.com>, <shawnguo@...nel.org>,
<arnd@...db.de>, <sudeep.holla@....com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC
Hi Krzysztof,
Thank you for your reply.
在 2023/7/17 20:06, Krzysztof Kozlowski 写道:
> On 14/07/2023 08:17, lihuisong (C) wrote:
>> Hi all,
>>
>> Can you take a look at this series?
> People you listed in "To:" field are not maintainers of HiSilicon, so
> why pinging us?
This "To:" field are from the get_maintainer.pl script.
./scripts/get_maintainer.pl -f ./drivers/soc/
The hisilicon in drivers/soc/ is created for the first time. So there
are no maintainer of HiSilicon.
Thanks for reminder.
add HiSilicon SOC maintainer Wei Xu.
>
> HiSilicon DTS has numerous issues, so if you want to increase the
> chances anyone cares about your patch, please contribute to fixing and
> improving your company DTS. See for example commit b2bbc8687 which is
> bad (underscores are not allowed) or 1860a51823 which is just wrong. The
> latter one is being fixed, although I do not see the fix being picked
> up... my feelings are the platform is just dead.
The HCCS driver has nothing to do with HiSilicon DTS.
So I cannot understand why you say DTS.
/Huisong
Powered by blists - more mailing lists