public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: ARM Maintainers <arm@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: update entry for entry for ARM/berlin
Date: Thu, 29 Mar 2018 13:46:36 +0200	[thread overview]
Message-ID: <87fu4jt883.fsf@bootlin.com> (raw)
In-Reply-To: <20180329164240.20cfddbc@xhacker.debian> (Jisheng Zhang's message of "Thu, 29 Mar 2018 16:42:40 +0800")

Hi Jisheng,
 
 On jeu., mars 29 2018, Jisheng Zhang <Jisheng.Zhang@synaptics.com> wrote:

> Change the entry name and move it to its alphabetical location.
> We move to ARM/Synaptics instead of ARM/Marvell.
>
> This patch also updates my email address from marvell to synaptics.
>
> Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> ---
>  MAINTAINERS | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6e950b8b4a41..0a0da6a8e607 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1578,15 +1578,6 @@ ARM/MAGICIAN MACHINE SUPPORT
>  M:	Philipp Zabel <philipp.zabel@gmail.com>
>  S:	Maintained
>  
> -ARM/Marvell Berlin SoC support
> -M:	Jisheng Zhang <jszhang@marvell.com>
> -M:	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> -L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> -S:	Maintained
> -F:	arch/arm/mach-berlin/
> -F:	arch/arm/boot/dts/berlin*
> -F:	arch/arm64/boot/dts/marvell/berlin*
> -
>  ARM/Marvell Dove/MV78xx0/Orion SOC support
>  M:	Jason Cooper <jason@lakedaemon.net>
>  M:	Andrew Lunn <andrew@lunn.ch>
> @@ -2006,6 +1997,15 @@ F:	arch/arm/boot/dts/stm32*
>  F:	arch/arm/mach-stm32/
>  F:	drivers/clocksource/armv7m_systick.c
>  
> +ARM/Synaptics Berlin SoC support
> +M:	Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> +M:	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> +L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +S:	Maintained
> +F:	arch/arm/mach-berlin/
> +F:	arch/arm/boot/dts/berlin*
> +F:	arch/arm64/boot/dts/marvell/berlin*

I though you had move the dts file from
arch/arm64/boot/dts/marvell/berlin* to arch/arm64/boot/dts/synatpics,
according a patch you submitted in September.

What happened?

Gregory

> +
>  ARM/TANGO ARCHITECTURE
>  M:	Marc Gonzalez <marc.w.gonzalez@free.fr>
>  M:	Mans Rullgard <mans@mansr.com>
> -- 
> 2.16.3
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  reply	other threads:[~2018-03-29 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  8:42 [PATCH] MAINTAINERS: update entry for entry for ARM/berlin Jisheng Zhang
2018-03-29 11:46 ` Gregory CLEMENT [this message]
2018-04-19  8:36   ` Jisheng Zhang
2018-03-29 13:08 ` Andrew Lunn
2018-03-30  3:19   ` Jisheng Zhang

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=87fu4jt883.fsf@bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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