devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clay Chang <clayc@hpe.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <soc@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <verdun@hpe.com>,
	<nick.hawkins@hpe.com>, <arnd@arndb.de>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <linux@armlinux.org.uk>,
	<olof@lixom.net>
Subject: Re: [PATCH 5/5] MAINTAINERS: Add maintainer of GXP SROM support
Date: Thu, 12 Jan 2023 21:18:15 +0800	[thread overview]
Message-ID: <Y8AIl4/J+YwsQrgF@enigma.ccjz.io> (raw)
In-Reply-To: <83e7b2b0-1840-bc8b-e657-ab94975b955d@linaro.org>

On Tue, Jan 10, 2023 at 10:51:00AM +0100, Krzysztof Kozlowski wrote:
> On 10/01/2023 05:25, clayc@hpe.com wrote:
> > From: Clay Chang <clayc@hpe.com>
> > 
> > Add Clay Chang as the maintainer of GXP SROM support.
> 
> Your commit is not doing it. Nope. Either make proper entry matching
> this commit msg or make commit msg reflecting truth.

Thank you for the comment. I will address this correctly in the next
revision.

> > 
> > Signed-off-by: Clay Chang <clayc@hpe.com>
> > ---
> >  MAINTAINERS | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ea941dc469fa..164571ac1cc5 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2279,14 +2279,22 @@ F:	arch/arm/mach-sa1100/jornada720.c
> >  ARM/HPE GXP ARCHITECTURE
> >  M:	Jean-Marie Verdun <verdun@hpe.com>
> >  M:	Nick Hawkins <nick.hawkins@hpe.com>
> > +M:	Clay Chang <clayc@hpe.com>
> 
> 
> Best regards,
> Krzysztof
> 

Thanks,
Clay

  reply	other threads:[~2023-01-12 13:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  4:25 [PATCH 0/5] ARM: Add GXP SROM Support clayc
2023-01-10  4:25 ` [PATCH 1/5] soc: hpe: Add GXP SROM Control Register Driver clayc
2023-01-10  9:46   ` Krzysztof Kozlowski
2023-01-12 12:46     ` Clay Chang
2023-01-10  4:25 ` [PATCH 2/5] dt-bindings: soc: hpe: hpe,gxp-srom.yaml clayc
2023-01-10  9:49   ` Krzysztof Kozlowski
2023-01-12 13:16     ` Clay Chang
2023-01-12 13:37       ` Arnd Bergmann
2023-01-16 13:42         ` Clay Chang
2023-01-16 15:18           ` Arnd Bergmann
2023-01-19  7:39             ` Clay Chang
2023-01-19  7:56               ` Arnd Bergmann
2023-01-10  4:25 ` [PATCH 3/5] ARM: dts: hpe: Add SROM Driver clayc
2023-01-10  4:25 ` [PATCH 4/5] ARM: multi_v7_defconfig: Add GXP " clayc
2023-01-10  9:50   ` Krzysztof Kozlowski
2023-01-12 13:17     ` Clay Chang
2023-01-10  4:25 ` [PATCH 5/5] MAINTAINERS: Add maintainer of GXP SROM support clayc
2023-01-10  9:51   ` Krzysztof Kozlowski
2023-01-12 13:18     ` Clay Chang [this message]
2023-01-20  2:21 ` [PATCH 0/5] ARM: Add GXP SROM Support Andrew Jeffery
2023-01-31 13:46   ` Clay Chang
2023-02-01 13:28     ` Clay Chang
2023-02-02  1:12       ` Andrew Jeffery
2023-02-02 15:25         ` Clay Chang

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=Y8AIl4/J+YwsQrgF@enigma.ccjz.io \
    --to=clayc@hpe.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=nick.hawkins@hpe.com \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=soc@kernel.org \
    --cc=verdun@hpe.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).