linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jnair@caviumnetworks.com (Jayachandran C)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/2] arm64: dts: move from ARCH_VULCAN to ARCH_THUNDER2
Date: Wed, 15 Mar 2017 08:15:12 +0000	[thread overview]
Message-ID: <20170315081431.GA2415@localhost> (raw)
In-Reply-To: <8262c276-c39c-17b6-dcb6-d087d68d3df5@gmail.com>

On Tue, Mar 14, 2017 at 11:16:47AM -0700, Florian Fainelli wrote:
> On 03/14/2017 05:47 AM, Jayachandran C wrote:
> > Move and update device tree files as part of transition from Broadcom
> > Vulcan to Cavium ThunderX2.
> > 
> > The changes are to:
> >  * rename dts/broadcom/vulcan.dtsi to cavium/thunder2-99xx.dtsi,
> >    update cpu cores to be "cavium,thunder2", and update SoC to be
> >    "cavium,thunderx2-cn9900"
> >  * move SoC dts/broadcom/vulcan-eval.dtsi to cavium/thunder2-99xx.dtsi
> >    and update board name string
> >  * Update dts/broadcom/Makefile not to build vulcan dtbs
> >  * Update dts/cavium/Makefile to build thunder2 dtbs
> > 
> > No changes to the dts contents except the updated "compatible" and
> > "model" properties.
> > 
> > Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
> > Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> 
> Can you also change the relevant entry in the MAINTAINERS file:
> 
> BROADCOM VULCAN ARM64 SOC
> M:      Jayachandran C. <c.jayachandran@gmail.com>
> M:      bcm-kernel-feedback-list at broadcom.com
> L:      linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> S:      Maintained
> F:      arch/arm64/boot/dts/broadcom/vulcan*

I was planning to remove this entry in the later patchset that removes
ARCH_VULCAN. But, as you suggest, it makes more sense to do that now.

I will post an updated patchset with a new patch to update the entry.
 
> With that fixed:
> 
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>

Thanks,
JC.

  reply	other threads:[~2017-03-15  8:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 10:03 [PATCH v5 0/2] ARCH_VULCAN to ARCH_THUNDER2 transition Jayachandran C
2017-03-12 10:03 ` [PATCH v5 1/2] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-03-12 10:03 ` [PATCH v5 2/2] arm64: dts: move from ARCH_VULCAN to ARCH_THUNDER2 Jayachandran C
2017-03-13 12:04   ` Matthias Brugger
2017-03-13 13:52     ` Jayachandran C
2017-03-14 12:47 ` [PATCH v6 0/2] ARCH_VULCAN to ARCH_THUNDER2 transition Jayachandran C
2017-03-14 12:47   ` [PATCH v6 1/2] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-03-14 12:47   ` [PATCH v6 2/2] arm64: dts: move from ARCH_VULCAN to ARCH_THUNDER2 Jayachandran C
2017-03-14 18:16     ` Florian Fainelli
2017-03-15  8:15       ` Jayachandran C [this message]
2017-03-31  9:44     ` Arnd Bergmann
2017-03-15 20:10   ` [PATCH v6 0/3] ARCH_VULCAN to ARCH_THUNDER2 transition Jayachandran C
2017-03-15 20:11     ` [PATCH v6 1/3] dt-bindings: Add arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-03-31  9:40       ` Arnd Bergmann
2017-03-15 20:11     ` [PATCH v6 2/3] arm64: dts: move from ARCH_VULCAN to ARCH_THUNDER2 Jayachandran C
2017-03-15 20:11     ` [PATCH v6 3/3] MAINTAINERS: Broadcom Vulcan is now Cavium ThunderX2 Jayachandran C
2017-03-30 15:40       ` 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=20170315081431.GA2415@localhost \
    --to=jnair@caviumnetworks.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).