From: zhiyong.tao <zhiyong.tao@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-rtc@vger.kernel.org, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, tinghan.shen@mediatek.com,
wen.su@mediatek.com, srv_heupstream@mediatek.com,
hui.liu@mediatek.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, macpaul.lin@mediatek.com,
sean.wang@mediatek.com, matthias.bgg@gmail.com,
eddie.huang@mediatek.com, lee.jones@linaro.org,
hsin-hsiung.wang@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: pmic: mt6366: add binding document
Date: Thu, 28 Jul 2022 14:02:25 +0800 [thread overview]
Message-ID: <b4468be380019ee53e00cb8df3942c195ce5ab2e.camel@mediatek.com> (raw)
In-Reply-To: <YnpNb258/JRSjZFQ@sirena.org.uk>
On Tue, 2022-05-10 at 12:33 +0100, Mark Brown wrote:
> 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.
==> Hi Mark,
we will fix it in v2
Thanks
prev parent reply other threads:[~2022-07-28 6:53 UTC|newest]
Thread overview: 10+ 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-07-28 6:06 ` zhiyong.tao
2022-05-10 10:14 ` Krzysztof Kozlowski
2022-07-28 6:00 ` zhiyong.tao
2022-05-10 11:33 ` Mark Brown
2022-07-28 6:02 ` zhiyong.tao [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=b4468be380019ee53e00cb8df3942c195ce5ab2e.camel@mediatek.com \
--to=zhiyong.tao@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--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 \
/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