From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm64: cputype info for Broadcom Vulcan
Date: Wed, 17 Feb 2016 17:26:00 +0000 [thread overview]
Message-ID: <20160217172600.GA26514@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <56C3C9D4.4020506@gmail.com>
On Tue, Feb 16, 2016 at 05:16:04PM -0800, Florian Fainelli wrote:
> On 15/02/16 02:12, Will Deacon wrote:
> > On Sun, Feb 14, 2016 at 12:16:35AM +0530, Jayachandran C wrote:
> >> Add Broadcom Vulcan implementor ID and part ID in cputype.h. This is
> >> to document the values.
> >>
> >> Signed-off-by: Jayachandran C <jchandra@broadcom.com>
> >> ---
> >> arch/arm64/include/asm/cputype.h | 2 ++
> >> 1 file changed, 2 insertions(+)
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Would this be picked by Calatin, or should this be sent along with the
> ARM/ARM64 SoC changes pull requests (just wondering?), thanks!
It can go via the arm-soc tree together with the other patches. If you
need another ack:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2016-02-17 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 18:46 [PATCH 0/4] Support for Broadcom Vulcan ARM64 processor Jayachandran C
2016-02-13 18:46 ` [PATCH 1/4] arm64: Broadcom Vulcan support Jayachandran C
2016-02-17 1:22 ` Florian Fainelli
2016-02-17 17:16 ` Mark Rutland
2016-02-19 6:58 ` Jayachandran Chandrashekaran Nair
2016-02-18 18:15 ` [1/4] " Ray Jui
2016-02-19 19:24 ` Florian Fainelli
2016-02-13 18:46 ` [PATCH 2/4] dt-bindings: Add documentation for Broadcom Vulcan Jayachandran C
2016-02-17 17:17 ` Mark Rutland
2016-02-13 18:46 ` [PATCH 3/4] arm64: defconfig: Add Broadcom Vulcan to defconfig Jayachandran C
2016-02-13 18:46 ` [PATCH 4/4] arm64: cputype info for Broadcom Vulcan Jayachandran C
2016-02-15 10:12 ` Will Deacon
2016-02-17 1:16 ` Florian Fainelli
2016-02-17 17:26 ` Catalin Marinas [this message]
2016-02-17 7:32 ` Zi Shen Lim
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=20160217172600.GA26514@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.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).