From: Julien Grall <julien.grall@linaro.org>
To: Jon Fraser <jfraser@broadcom.com>,
xen-devel@lists.xen.org, Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support.
Date: Wed, 01 Oct 2014 16:28:00 +0100 [thread overview]
Message-ID: <542C1D80.6070804@linaro.org> (raw)
In-Reply-To: <1412117825-8228-1-git-send-email-jfraser@broadcom.com>
Hello Jon,
Thank you for adding support to a new board in Xen.
I don't find a cover letter, so I will make general comments here.
It's common to CC the relevant maintainers on the different patches. So,
we can directly now that we are concerned with the series. You can use
scripts/get_maintainers.pl for this purpose.
Also, I've noticed that your patches are not arrived threaded in my box,
it's harder for us to know that every patches belongs to the same
series. git send-email *your list of patch* should do the job for you.
On 09/30/2014 11:57 PM, Jon Fraser wrote:
> Relax cpu id mask to cover minor cpu revisions in the SoC versions.
>
> Signed-off-by: Jon Fraser <jfraser@broadcom.com>
Reviewed-by: Julien Grall <julien.grall@linaro.org>
> ---
> xen/arch/arm/arm32/proc-v7.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/xen/arch/arm/arm32/proc-v7.S b/xen/arch/arm/arm32/proc-v7.S
> index b0d5343..2f3ff1e 100644
> --- a/xen/arch/arm/arm32/proc-v7.S
> +++ b/xen/arch/arm/arm32/proc-v7.S
> @@ -50,8 +50,8 @@ __v7_ca7mp_proc_info:
> .section ".init.proc.info", #alloc, #execinstr
> .type __v7_brahma15mp_proc_info, #object
> __v7_brahma15mp_proc_info:
> - .long 0x420F00F2 /* Broadcom Brahma-B15 */
> - .long 0xFF0FFFFF /* Mask */
> + .long 0x420F00F0 /* Broadcom Brahma-B15 */
> + .long 0xFF0FFFF0 /* Mask */
> .long brahma15mp_init
> .long caxx_processor
> .size __v7_brahma15mp_proc_info, . - __v7_brahma15mp_proc_info
>
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-10-01 15:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 22:57 [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-01 15:28 ` Julien Grall [this message]
2014-10-02 22:16 ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Jon Fraser
2014-10-02 22:16 ` [PATCH V2 1/4] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-03 10:39 ` Julien Grall
2014-10-02 22:16 ` [PATCH V2 2/4] xen/arm: Update early print console UART address for Broadcom 7445D0 Jon Fraser
2014-10-02 22:16 ` [PATCH V2 3/4] xen/arm: Add support for Broadcom 7445D0 A15 platform Jon Fraser
2014-10-03 10:44 ` Julien Grall
2014-10-03 15:15 ` Jonathan Fraser
2014-10-03 15:22 ` Ian Campbell
2014-10-03 15:45 ` Jonathan Fraser
2014-10-02 22:16 ` [PATCH V2 4/4] xen/arm/docs: Document Broadcom 7445D0 early printk support Jon Fraser
2014-10-03 10:41 ` Julien Grall
2014-10-03 10:29 ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Ian Campbell
2014-10-03 10:42 ` Julien Grall
2014-10-03 15:03 ` Jonathan Fraser
2014-10-03 15:29 ` Ian Campbell
2014-10-02 12:57 ` [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Ian Campbell
2014-10-02 15:09 ` Konrad Rzeszutek Wilk
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=542C1D80.6070804@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=jfraser@broadcom.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).