From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for the upcoming Maili SoC
Date: Sat, 30 May 2026 12:42:12 +0200 [thread overview]
Message-ID: <20260530-primitive-encouraging-quail-ee8af1@quoll> (raw)
In-Reply-To: <20260522-maili-pinctrl-v1-0-0a6636f5c277@oss.qualcomm.com>
On Fri, May 22, 2026 at 12:42:07AM -0700, Jingyi Wang wrote:
> Introduce Top Level Mode Multiplexer dt-binding and driver for the
> upcoming Qualcomm Maili SoC.
This is the first patch where such name appears, so same comments as
before for other cases - describe what is Maili somewhere.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-30 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 7:42 [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for the upcoming Maili SoC Jingyi Wang
2026-05-22 7:42 ` [PATCH 1/2] dt-bindings: pinctrl: qcom: Describe Maili TLMM block Jingyi Wang
2026-05-22 7:57 ` sashiko-bot
2026-05-30 10:43 ` Krzysztof Kozlowski
2026-05-22 7:42 ` [PATCH 2/2] pinctrl: qcom: Add the tlmm driver for Maili platform Jingyi Wang
2026-06-10 8:08 ` Sneh Mankad
2026-06-15 2:34 ` Jingyi Wang
2026-05-30 10:42 ` Krzysztof Kozlowski [this message]
2026-06-01 6:15 ` [PATCH 0/2] pinctrl: qcom: Introduce Pinctrl for the upcoming Maili SoC Jingyi Wang
2026-06-01 8:38 ` Krzysztof Kozlowski
2026-06-05 5:54 ` Jingyi Wang
2026-06-05 8:04 ` Krzysztof Kozlowski
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=20260530-primitive-encouraging-quail-ee8af1@quoll \
--to=krzk@kernel.org \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.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