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: [PATCH v2] MAINTAINERS: update entry for ARM/berlin
Date: Mon, 2 Apr 2018 10:28:31 +0800	[thread overview]
Message-ID: <20180402102819.599ac67f@xhacker.debian> (raw)
In-Reply-To: <20180330135932.GB28244@lunn.ch>

On Fri, 30 Mar 2018 15:59:32 +0200 Andrew Lunn wrote:

> On Fri, Mar 30, 2018 at 11:02:11AM +0800, Jisheng Zhang wrote:
> > 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>  
> 
> Thanks for the link
> 
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> 
> Do you still plan to move the DT files from the Marvell subdirectory?
> Are the locations of these files considered fixed?
> 

For new SoCs, the DT files will be put into synaptics sub-directory.
But for existing arm64 berlin DT files which currently sits in
arch/arm64/boot/dts/marvell, I dunno the proper solution. Could
you please give some suggestions? How do other vendors handle this
situation in the past?

Thanks in advance,
Jisheng

  reply	other threads:[~2018-04-02  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  3:02 [PATCH v2] MAINTAINERS: update entry for ARM/berlin Jisheng Zhang
2018-03-30 13:59 ` Andrew Lunn
2018-04-02  2:28   ` Jisheng Zhang [this message]
2018-04-04 12:03     ` Arnd Bergmann
2018-04-05  9:08   ` Arnd Bergmann

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=20180402102819.599ac67f@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).