linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: Bad MAINTAINERS pattern in section 'ARM/Synaptics Berlin SoC support'
Date: Sat, 29 Sep 2018 10:04:36 +0800	[thread overview]
Message-ID: <20180929100436.08f931df@xhacker.debian> (raw)
In-Reply-To: <20180928215132.28867-1-joe@perches.com>

On Fri, 28 Sep 2018 14:51:32 -0700 Joe Perches <joe@perches.com> wrote:

> Please fix this defect appropriately.
> 
> linux-next MAINTAINERS section:
> 
> 	2111	ARM/Synaptics Berlin SoC support
> 	2112	M:	Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> 	2113	M:	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> 	2114	L:	linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> 	2115	S:	Maintained
> 	2116	F:	arch/arm/mach-berlin/
> 	2117	F:	arch/arm/boot/dts/berlin*
> -->	2118	F:	arch/arm64/boot/dts/marvell/berlin*  

Thanks so much. I will fix it soon.

> 
> Commit that introduced this:
> 
> commit bc52497a595d2246923749177d99e4216703b0f4
>  Author: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
>  Date:   Fri Mar 30 11:02:11 2018 +0800
>  
>      MAINTAINERS: update entry for ARM/berlin
>      
>      Synaptics has acquired the Multimedia Solutions Business of Marvell[1].
>      So change the berlin 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.
>      
>      [1] https://www.synaptics.com/company/news/conexant-marvell
>      
>      Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
>      Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>      Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>  
>   MAINTAINERS | 18 +++++++++---------
>   1 file changed, 9 insertions(+), 9 deletions(-)
> 
> Last commit with arch/arm64/boot/dts/marvell/berlin*
> 
> commit 031106ce95a201f6dd4c5ebf35abb900cf34e2ba
> Author: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> Date:   Wed May 16 17:43:28 2018 +0800
> 
>     arm64: dts: move berlin SoC files from marvell dir to synaptics dir
>     
>     Move device tree files as part of transition from Marvell berlin to
>     Synaptics berlin.
>     
>     Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
> 
>  arch/arm64/boot/dts/Makefile                                 | 1 +
>  arch/arm64/boot/dts/marvell/Makefile                         | 4 ----
>  arch/arm64/boot/dts/synaptics/Makefile                       | 4 ++++
>  arch/arm64/boot/dts/{marvell => synaptics}/berlin4ct-dmp.dts | 0
>  arch/arm64/boot/dts/{marvell => synaptics}/berlin4ct-stb.dts | 0
>  arch/arm64/boot/dts/{marvell => synaptics}/berlin4ct.dtsi    | 0
>  6 files changed, 5 insertions(+), 4 deletions(-)

      reply	other threads:[~2018-09-29  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 21:51 Bad MAINTAINERS pattern in section 'ARM/Synaptics Berlin SoC support' Joe Perches
2018-09-29  2:04 ` Jisheng Zhang [this message]

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=20180929100436.08f931df@xhacker.debian \
    --to=jisheng.zhang@synaptics.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).