All of lore.kernel.org
 help / color / mirror / Atom feed
From: "long.wanglong" <long.wanglong@huawei.com>
To: Haojian Zhuang <haojian.zhuang@linaro.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<peifeiyue@huawei.com>
Subject: Re: [PATCH] irq: irq-hip04: initialize hip04_cpu_map to 0xffff
Date: Sun, 4 Jan 2015 12:08:20 +0800	[thread overview]
Message-ID: <54A8BCB4.4010801@huawei.com> (raw)
In-Reply-To: <CAD6h2NSnU5aLEC2w12FVesvBHoKHg2DNY3Eav-kq7htivu=Z=w@mail.gmail.com>

On 2014/12/11 19:19, Haojian Zhuang wrote:
> On 11 December 2014 at 19:03, Wang Long <long.wanglong@huawei.com> wrote:
>> HiP04 GIC extends to support 16 cores, so we should
>> initialize the hip04_cpu_map to 0xffff.
>>
>> Signed-off-by: Wang Long <long.wanglong@huawei.com>
>> ---
>>  drivers/irqchip/irq-hip04.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/irqchip/irq-hip04.c b/drivers/irqchip/irq-hip04.c
>> index 9c8f8335..8eee46b 100644
>> --- a/drivers/irqchip/irq-hip04.c
>> +++ b/drivers/irqchip/irq-hip04.c
>> @@ -382,7 +382,7 @@ hip04_of_init(struct device_node *node, struct device_node *parent)
>>          * It will be refined as each CPU probes its ID.
>>          */
>>         for (i = 0; i < NR_HIP04_CPU_IF; i++)
>> -               hip04_cpu_map[i] = 0xff;
>> +               hip04_cpu_map[i] = 0xffff;
>>
>>         /*
>>          * Find out how many interrupts are supported.
>> --
>> 1.8.3.4
>>
> 
> Acked-by: Haojian Zhuang <haojian.zhuang@linaro.org>
> 
> Best Regards
> Haojian
> 
> 

hi Thomas Gleixner, Jason Cooper

could you please help to apply this patch?

Best Regards
Wang Long



  reply	other threads:[~2015-01-04  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:03 [PATCH] irq: irq-hip04: initialize hip04_cpu_map to 0xffff Wang Long
2014-12-11 11:19 ` Haojian Zhuang
2015-01-04  4:08   ` long.wanglong [this message]
2015-01-07  2:17 ` Jason Cooper

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=54A8BCB4.4010801@huawei.com \
    --to=long.wanglong@huawei.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peifeiyue@huawei.com \
    --cc=tglx@linutronix.de \
    /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.