[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdae5678-ff79-4c04-8d77-c6bdfe613c68@kernel.org>
Date: Sun, 9 Feb 2025 11:48:50 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Crystal Guo <crystal.guo@...iatek.com>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Matthias Brugger
<matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [v2,2/2] dt-bindings: memory-controllers: Add MediaTek DRAM
controller interface
On 06/02/2025 13:16, Crystal Guo wrote:
> A MediaTek DRAM controller interface to provide the current DDR data rate.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Signed-off-by: Crystal Guo <crystal.guo@...iatek.com>
> ---
> .../mediatek,common-dramc.yaml | 129 ------------------
Why is there removal here if you add? Commit msg explains nothing here.
Why this patch was sent twice?
Please use standard email subjects, so with the PATCH keyword in the
title. `git format-patch -vX` helps here to create proper versioned
patches. Another useful tool is b4. Skipping the PATCH keyword makes
filtering of emails more difficult thus making the review process less
convenient.
Best regards,
Krzysztof
Powered by blists - more mailing lists