From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "allen-kh.cheng" <allen-kh.cheng@mediatek.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH] dt-bindings: pwm: mtk-disp: add compatible string for MT8183 SoC
Date: Tue, 8 Feb 2022 10:10:29 +0100 [thread overview]
Message-ID: <20220208091029.iwnepc343djtcvq5@pengutronix.de> (raw)
In-Reply-To: <f6633fc82c4fa899c7f4ca27d9751d9e61fb90ac.camel@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hello,
On Tue, Feb 08, 2022 at 12:28:23PM +0800, allen-kh.cheng wrote:
> Thank you for your suggestions.
> We will send another patch for .yaml format.
>
> About the last reminder, sorry, I don’t get that.
> Do you mean upper/lower case letters in an email address?
exactly. I don't know how picky Thierry (who is responsible to pick up
this patch or not) is, but a 100% match is the safe bet.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-08 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 11:26 [PATCH] dt-bindings: pwm: mtk-disp: add compatible string for MT8183 SoC Allen-KH Cheng
2022-02-07 12:51 ` Uwe Kleine-König
[not found] ` <f6633fc82c4fa899c7f4ca27d9751d9e61fb90ac.camel@mediatek.com>
2022-02-08 9:10 ` Uwe Kleine-König [this message]
2022-02-24 13:27 ` Thierry Reding
2022-02-11 16:24 ` Rob Herring
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=20220208091029.iwnepc343djtcvq5@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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).