From: xuwei5@hisilicon•com (Wei Xu)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL]Hisilicon hip04 soc and D01 board DT updates for v4.2
Date: Wed, 13 May 2015 23:19:50 +0100 [thread overview]
Message-ID: <5553CE06.1000605@hisilicon.com> (raw)
In-Reply-To: <2178083.0uhiGDS5Eh@wuerfel>
On 5/13/2015 8:31 PM, Arnd Bergmann wrote:
> On Wednesday 13 May 2015 12:20:28 Tyler Baker wrote:
>> On 12 May 2015 at 08:09, Wei Xu <xuwei5@hisilicon•com> wrote:
>>> On 5/12/2015 4:06 PM, Arnd Bergmann wrote:
>>>> On Friday 08 May 2015 15:26:09 Wei Xu wrote:
>>>>> ARM: DT: Hisilicon hip04 soc and D01 board updates for 4.2
>>>>>
>>>>> - Add hip04 GPIO nodes
>>>>> - Add NANDC nodes for hip04 and D01 board
>>>>> - Add hip04 ethernet related nodes
>>>>>
>>
>> When this was pulled into arm-soc, the kernelci.org bot reported
>> hip04-d01 boot failures[1]. Before bisecting, I decided to wait a day
>> and double check the status of -next in case there were needed
>> dependencies from other trees. However, now there are the same
>> hip04-d01 boot failures in next-20150513[2]. My robot has bisected[3]
>> these boot failures down to...
>>
>> 828fcfe3c84ade68ecc3f1ba78baebc1654977f3 is the first bad commit
>> commit 828fcfe3c84ade68ecc3f1ba78baebc1654977f3
>> Author: Zhou Wang <wangzhou.bry@gmail•com>
>> Date: Wed Mar 25 14:57:45 2015 +0800
>>
>> ARM: dts: hip04: add GPIO pieces
>>
>> Hisilicon Soc hip04 has four GPIO controllers, each one has 32
>> GPIOs and can be configured to be an interrupt controller.The GPIO
>> controllers are compatible with the snps,dw-apb-gpio driver.
>> This patch add the corresponding device tree nodes.
>>
>> Acked-by: Linus Walleij <linus.walleij@linaro•org>
>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon•com>
>> Signed-off-by: Wei Xu <xuwei5@hisilicon•com>
>>
>> This commit does not revert cleanly from -next, so I reverted all
>> three commits in this pull request on top of next-20150513 and this
>> get the hip04-d01 booting again.
>>
>
> Ok, thanks for the report!
Hi Tyler,
Thanks for the report!
I will reconfirm it again.
Hi Arnd,
> Wei, can you send a bug fix, or should I revert that branch for now?
I will try to resolve it tomorrow.
If I could not resolve it by the end of tomorrow,
I will send a mail to you to ask for reverting.
Do you think is it OK?
Thanks!
Best Regards,
Wei
> Arnd
>
> .
>
next prev parent reply other threads:[~2015-05-13 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 14:26 [GIT PULL]Hisilicon hip04 soc and D01 board DT updates for v4.2 Wei Xu
2015-05-12 15:06 ` Arnd Bergmann
2015-05-12 15:09 ` Wei Xu
2015-05-13 19:20 ` Tyler Baker
2015-05-13 19:31 ` Arnd Bergmann
2015-05-13 22:19 ` Wei Xu [this message]
2015-05-14 7:18 ` Arnd Bergmann
2015-05-14 8:49 ` Wei Xu
2015-05-14 13:36 ` Tyler Baker
2015-05-14 13:55 ` Tyler Baker
2015-05-14 17:49 ` Wei Xu
2015-05-15 9:28 ` Arnd Bergmann
2015-06-25 0:24 ` Kevin Hilman
2015-06-25 7:57 ` Wei Xu
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=5553CE06.1000605@hisilicon.com \
--to=xuwei5@hisilicon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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