[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3dbff750-c430-04a7-1c53-f2e327e54f2e@linaro.org>
Date: Sun, 17 Sep 2023 10:31:26 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: William-tw Lin <william-tw.lin@...iatek.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Kevin Hilman <khilman@...nel.org>
Cc: Project_Global_Chrome_Upstream_Group@...iatek.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v2 0/3] mtk-socinfo driver implementation
On 15/09/2023 17:26, William-tw Lin wrote:
> This purpose of the patches is for soc-related information retrival.
> Such information includes manufacturer information, SoC name, SoC
> segment name, and SoC marketing name.
>
> Based on tag: next-20230915, linux-next/master
>
> Changes in v2:
> - Remove mtk-socinfo.h
> - Consolidate different compatibles into mediatek,socinfo
> - Move socinfo node out of MMIO bus
> - Move mtk-socinfo.yaml to hwinfo
> - Fix reviewer's comments
This is way to vague, especially that you did not fix them. You need to
list all of them. Then we will nicely see what you ignored.
Best regards,
Krzysztof
Powered by blists - more mailing lists