From: Krzysztof Kozlowski <krzk@kernel.org>
To: Congcong Yao <Congcong.Yao@mediatek.com>,
Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
jarried.lin@mediatek.com, vince-wl.liu@mediatek.com,
justin.yeh@mediatek.com
Subject: Re: [PATCH v3 0/2] MT8189 SMI SUPPORT
Date: Wed, 8 Jul 2026 13:12:50 +0200 [thread overview]
Message-ID: <cf776c64-40dc-437c-8891-8e7d6d122802@kernel.org> (raw)
In-Reply-To: <20260701074533.175803-1-Congcong.Yao@mediatek.com>
On 01/07/2026 09:44, Congcong Yao wrote:
> Based on tag: next-20260629, linux-next/master
>
> This patchset add mt8189 smi support.
b4 diff '<20260701074533.175803-2-Congcong.Yao@mediatek.com>'
Looking up
https://lore.kernel.org/all/20260701074533.175803-2-Congcong.Yao@mediatek.com/
Grabbing thread from
lore.kernel.org/all/20260701074533.175803-2-Congcong.Yao@mediatek.com/t.mbox.gz
Checking for older revisions
Grabbing search results from lore.kernel.org
---
Analyzing 5 messages in the thread
Could not find lower series to compare against.
I also do not see that you used b4 to submit. You are not making
maintainer life easier. I will get back to this much later.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-08 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 7:44 [PATCH v3 0/2] MT8189 SMI SUPPORT Congcong Yao
2026-07-01 7:44 ` [PATCH v3 1/2] dt-bindings: memory-controllers: mtk-smi: Add support for mt8189 Congcong Yao
2026-07-01 7:44 ` [PATCH v3 2/2] memory: mtk-smi: Add mt8189 support Congcong Yao
2026-07-08 11:12 ` Krzysztof Kozlowski [this message]
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=cf776c64-40dc-437c-8891-8e7d6d122802@kernel.org \
--to=krzk@kernel.org \
--cc=Congcong.Yao@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarried.lin@mediatek.com \
--cc=justin.yeh@mediatek.com \
--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 \
--cc=vince-wl.liu@mediatek.com \
--cc=yong.wu@mediatek.com \
/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