From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm64: cputype info for Broadcom Vulcan
Date: Tue, 16 Feb 2016 17:16:04 -0800 [thread overview]
Message-ID: <56C3C9D4.4020506@gmail.com> (raw)
In-Reply-To: <20160215101235.GA1748@arm.com>
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!
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
Jayachandran C <jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 4/4] arm64: cputype info for Broadcom Vulcan
Date: Tue, 16 Feb 2016 17:16:04 -0800 [thread overview]
Message-ID: <56C3C9D4.4020506@gmail.com> (raw)
In-Reply-To: <20160215101235.GA1748-5wv7dgnIgG8@public.gmane.org>
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-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
>> ---
>> arch/arm64/include/asm/cputype.h | 2 ++
>> 1 file changed, 2 insertions(+)
>
> Acked-by: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Would this be picked by Calatin, or should this be sent along with the
ARM/ARM64 SoC changes pull requests (just wondering?), thanks!
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-17 1:16 UTC|newest]
Thread overview: 30+ 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 ` Jayachandran C
2016-02-13 18:46 ` [PATCH 1/4] arm64: Broadcom Vulcan support Jayachandran C
2016-02-13 18:46 ` Jayachandran C
2016-02-17 1:22 ` Florian Fainelli
2016-02-17 1:22 ` Florian Fainelli
2016-02-17 17:16 ` Mark Rutland
2016-02-17 17:16 ` Mark Rutland
2016-02-19 6:58 ` Jayachandran Chandrashekaran Nair
2016-02-19 6:58 ` Jayachandran Chandrashekaran Nair
2016-02-18 18:15 ` [1/4] " Ray Jui
2016-02-18 18:15 ` Ray Jui
2016-02-19 19:24 ` Florian Fainelli
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-13 18:46 ` Jayachandran C
2016-02-17 17:17 ` Mark Rutland
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 ` Jayachandran C
2016-02-13 18:46 ` [PATCH 4/4] arm64: cputype info for Broadcom Vulcan Jayachandran C
2016-02-13 18:46 ` Jayachandran C
2016-02-15 10:12 ` Will Deacon
2016-02-15 10:12 ` Will Deacon
2016-02-17 1:16 ` Florian Fainelli [this message]
2016-02-17 1:16 ` Florian Fainelli
2016-02-17 17:26 ` Catalin Marinas
2016-02-17 17:26 ` Catalin Marinas
2016-02-17 7:32 ` Zi Shen Lim
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=56C3C9D4.4020506@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.