From: Krzysztof Kozlowski <krzk@kernel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Crystal Guo <crystal.guo@mediatek.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [v3,1/2] dt-bindings: memory-controllers: Add MediaTek DRAM controller interface
Date: Wed, 26 Mar 2025 11:27:24 +0100 [thread overview]
Message-ID: <12f9b9ca-330b-4417-a805-da3880bc168f@kernel.org> (raw)
In-Reply-To: <6e7ad33d-c0e3-4160-81c3-93f6c88976ae@collabora.com>
On 26/03/2025 11:17, AngeloGioacchino Del Regno wrote:
> Il 26/03/25 08:56, Krzysztof Kozlowski ha scritto:
>> On Wed, Mar 26, 2025 at 02:30:31PM +0800, Crystal Guo wrote:
>>> A MediaTek DRAM controller interface to provide the current DDR
>>> data rate.
>>>
>>> Signed-off-by: Crystal Guo <crystal.guo@mediatek.com>
>>> ---
>>> .../memory-controllers/mediatek,dramc.yaml | 44 +++++++++++++++++++
>>> 1 file changed, 44 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/memory-controllers/mediatek,dramc.yaml
>>
>> Where is the rest of the patchset in DT patchwork? Where is any
>> changelog? Cover letter? What changed here?
>>
>> I receive dozen or hundreds of emails, so if you want to make
>> it difficult for me to review, I will just ignore the patch.
>>
>> I mark it as changes requested.
>>
>
> Krzysztof, I do see that devicetree cc'ed in all of the patches that Crystal
> sent - including the cover letter... and the cover letter has a changelog... :-)
>
> Was there any temporary issue with the DT patchwork or something, maybe?
>
> I anyway had to request some changes so no worries.
I was not precise. Rob's DT review process, which I also use, fetches
entire thread with b4 and then runs local mail client (mutt) on it. I
got only the binding patch. I see entire thread on my other mail client
(I often don't connect these in my brain), so indeed no clue what happened.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-26 10:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 6:30 [v3,0/2] Add an interface to get current DDR data rate Crystal Guo
2025-03-26 6:30 ` [v3,1/2] dt-bindings: memory-controllers: Add MediaTek DRAM controller interface Crystal Guo
2025-03-26 7:56 ` Krzysztof Kozlowski
2025-03-26 10:17 ` AngeloGioacchino Del Regno
2025-03-26 10:27 ` Krzysztof Kozlowski [this message]
2025-03-26 10:18 ` AngeloGioacchino Del Regno
2025-04-02 3:51 ` Crystal Guo (郭晶)
2025-04-02 9:24 ` AngeloGioacchino Del Regno
2025-03-26 6:30 ` [v3,2/2] memory/mediatek: Add an interface to get current DDR data rate Crystal Guo
2025-03-26 10:27 ` AngeloGioacchino Del Regno
2025-04-02 3:36 ` Crystal Guo (郭晶)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12f9b9ca-330b-4417-a805-da3880bc168f@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=crystal.guo@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox