From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Add Cavium ARCH_THUNDER2 platform
Date: Sat, 4 Feb 2017 19:11:17 -0800 [thread overview]
Message-ID: <db4646cc-b020-aa9f-7ab1-54bfca6e1588@gmail.com> (raw)
In-Reply-To: <1486256226-43889-1-git-send-email-jnair@caviumnetworks.com>
Le 02/04/17 ? 16:57, Jayachandran C a ?crit :
> Here's the updated patchset, please let me know if thereare any
> comments. If a pull request is needed(with a public git tree), I
> can set one up on github.
>
> This patchset adds support for the new ThunderX2 CN99XX processor
> family.
>
> Changes are to add: the config option, the required device tree files,
> the device tree bindings documentation and the defconfig entry.
>
> Changes from v1 -> v2:
> * split Kconfig.platforms changes and device tree changes
> * Added MAINTAINERS entry
Does that mean support for Broadcom Vulcan should be removed then? If
do, do you mind doing that?
--
Florian
next prev parent reply other threads:[~2017-02-05 3:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 0:57 [PATCH v2 0/5] Add Cavium ARCH_THUNDER2 platform Jayachandran C
2017-02-05 0:57 ` [PATCH v2 1/5] arm64: add THUNDER2 processor family Jayachandran C
2017-02-09 15:25 ` Arnd Bergmann
2017-02-05 0:57 ` [PATCH v2 2/5] MAINTAINERS: Add Cavium ThunderX2 entry Jayachandran C
2017-02-09 15:26 ` Arnd Bergmann
2017-02-05 0:57 ` [PATCH v2 3/5] arm64: dts: add device trees for ARCH_THUNDER2 Jayachandran C
2017-02-05 0:57 ` [PATCH v2 4/5] dt-bindings: arm64 ARCH_THUNDER2 platform documentation Jayachandran C
2017-02-05 0:57 ` [PATCH v2 5/5] arm64: add ARCH_THUNDER2 to defconfig Jayachandran C
2017-02-09 15:26 ` Arnd Bergmann
2017-02-05 3:11 ` Florian Fainelli [this message]
2017-02-05 9:19 ` [PATCH v2 0/5] Add Cavium ARCH_THUNDER2 platform Jayachandran C
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=db4646cc-b020-aa9f-7ab1-54bfca6e1588@gmail.com \
--to=f.fainelli@gmail.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).