From: Mark Brown <broonie@kernel.org>
To: Zhiyong Tao <zhiyong.tao@mediatek.com>
Cc: lee.jones@linaro.org, robh+dt@kernel.org, matthias.bgg@gmail.com,
lgirdwood@gmail.com, eddie.huang@mediatek.com,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
fshao@chromium.org, srv_heupstream@mediatek.com,
hui.liu@mediatek.com, tinghan.shen@mediatek.com,
hsin-hsiung.wang@mediatek.com, sean.wang@mediatek.com,
macpaul.lin@mediatek.com, wen.su@mediatek.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: pmic: mt6366: add binding document
Date: Tue, 10 May 2022 12:33:03 +0100 [thread overview]
Message-ID: <YnpNb258/JRSjZFQ@sirena.org.uk> (raw)
In-Reply-To: <20220510064603.15920-2-zhiyong.tao@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Tue, May 10, 2022 at 02:46:03PM +0800, Zhiyong Tao wrote:
> From: "Zhiyong.Tao" <zhiyong.tao@mediatek.com>
>
> The commit adds mt6366 binding document.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-10 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 6:46 [PATCH v1 0/1] Mediatek MT6366 PMIC patch Zhiyong Tao
2022-05-10 6:46 ` [PATCH] dt-bindings: pmic: mt6366: add binding document Zhiyong Tao
2022-05-10 7:56 ` Rex-BC Chen
2022-05-11 15:36 ` Krzysztof Kozlowski
2022-05-12 2:15 ` Rex-BC Chen
2022-05-10 10:14 ` Krzysztof Kozlowski
2022-05-10 11:33 ` Mark Brown [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=YnpNb258/JRSjZFQ@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=fshao@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=hui.liu@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tinghan.shen@mediatek.com \
--cc=wen.su@mediatek.com \
--cc=zhiyong.tao@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;
as well as URLs for NNTP newsgroup(s).