[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YheH3uAzJCoPVyin@orome>
Date: Thu, 24 Feb 2022 14:27:58 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: "allen-kh.cheng" <allen-kh.cheng@...iatek.com>,
Lee Jones <lee.jones@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-pwm@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH] dt-bindings: pwm: mtk-disp: add compatible string for
MT8183 SoC
On Tue, Feb 08, 2022 at 10:10:29AM +0100, Uwe Kleine-König wrote:
> 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.
Email isn't generally case sensitive, so I don't care all that much if
they case differs. Ultimately the username part of an email address and
the domain should match to clarify that both are the same person.
There are also circumstances where it can make sense to have sender and
author differ, like for example if your corporate email tends to butcher
patches.
In this case it's fairly obvious that sender and author are the same
person, so I've applied this as-is.
Thanks,
Thierry
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists