public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: "Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] dt-bindings: usb: mtu3: add compatible for mt8186
Date: Fri, 25 Nov 2022 08:41:16 +0000	[thread overview]
Message-ID: <fc0cb10747056f8f38a077b39df3a83e6b340c64.camel@mediatek.com> (raw)
In-Reply-To: <4ffbba83-d23c-59ef-0b01-eeb80ea70219@linaro.org>

Hi Krzysztof,

I have used get_maintainers.pl to get the email address and apologize
for not seeing the difference.

Do you mean "+dt" in email address?

Best regards,
Allen

On Fri, 2022-11-25 at 09:00 +0100, Krzysztof Kozlowski wrote:
> On 23/11/2022 14:55, Allen-KH Cheng wrote:
> > Add a new compatible for mt8186 SoC.
> > 
> > Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> > ---
> >  Documentation/devicetree/bindings/usb/mediatek,mtu3.yaml | 1 +
> 
> Any reason for using different email address than what
> get_maintainers.pl prints?
> 
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2022-11-25  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221123135531.23221-1-allen-kh.cheng@mediatek.com>
     [not found] ` <20221123135531.23221-3-allen-kh.cheng@mediatek.com>
2022-11-23 15:23   ` [PATCH v2 2/5] arm64: dts: mt8186: Add power domains controller Matthias Brugger
     [not found] ` <20221123135531.23221-4-allen-kh.cheng@mediatek.com>
2022-11-23 15:28   ` [PATCH v2 3/5] arm64: dts: mt8186: Add IOMMU and SMI nodes Matthias Brugger
     [not found] ` <20221123135531.23221-5-allen-kh.cheng@mediatek.com>
2022-11-23 15:30   ` [PATCH v2 4/5] arm64: dts: mt8186: Add dsi node Matthias Brugger
     [not found] ` <20221123135531.23221-2-allen-kh.cheng@mediatek.com>
2022-11-23 15:11   ` [PATCH v2 1/5] dt-bindings: usb: mtu3: add compatible for mt8186 Matthias Brugger
2022-11-25  8:00   ` Krzysztof Kozlowski
2022-11-25  8:41     ` Allen-KH Cheng (程冠勳) [this message]
2022-11-25  8:59       ` Krzysztof Kozlowski
2022-11-25  9:02         ` Allen-KH Cheng (程冠勳)

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=fc0cb10747056f8f38a077b39df3a83e6b340c64.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsinyi@chromium.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    /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