From: Rong Chen <rong.a.chen@intel.com>
To: "Rafał Miłecki" <rafal@milecki.pl>, "kernel test robot" <lkp@intel.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
kbuild-all@lists.01.org, "Hauke Mehrtens" <hauke@hauke-m.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [kbuild-all] Re: [PATCH] ARM: dts: BCM5301X: Enable USB 3 PHY on Luxul XWR-3150
Date: Mon, 16 Nov 2020 14:14:54 +0800 [thread overview]
Message-ID: <93f6e8ad-be48-76f3-ada7-dcb72fc9abaf@intel.com> (raw)
In-Reply-To: <2d13b0399c717e410c129b5f1f67ab8f@milecki.pl>
On 11/13/20 9:51 PM, Rafał Miłecki wrote:
> Hey,
>
> On 2020-11-13 14:41, kernel test robot wrote:
>> [auto build test ERROR on robh/for-next]
>> [also build test ERROR on v5.10-rc3 next-20201113]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/ARM-dts-BCM5301X-Enable-USB-3-PHY-on-Luxul-XWR-3150/20201113-175236
>>
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
>> for-next
>> config: arm-randconfig-r036-20201113 (attached as .config)
>> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
>> reproduce (this is a W=1 build):
>> wget
>> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross
>> -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> #
>> https://github.com/0day-ci/linux/commit/1f7742592f638fdb90b7270d80d0c797e243ada7
>>
>> git remote add linux-review https://github.com/0day-ci/linux
>> git fetch --no-tags linux-review
>> Rafa-Mi-ecki/ARM-dts-BCM5301X-Enable-USB-3-PHY-on-Luxul-XWR-3150/20201113-175236
>>
>> git checkout 1f7742592f638fdb90b7270d80d0c797e243ada7
>> # save the attached .config to linux build tree
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0
>> make.cross ARCH=arm
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> Error: arch/arm/boot/dts/bcm47094-luxul-xwr-3150-v1.dts:78.1-9
>>>> syntax error
>> FATAL ERROR: Unable to parse input tree
>
> Is there a problem with bot or GitHub? I can't access any:
>
> https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/ARM-dts-BCM5301X-Enable-USB-3-PHY-on-Luxul-XWR-3150/20201113-175236
>
> https://github.com/0day-ci/linux/commit/1f7742592f638fdb90b7270d80d0c797e243ada7
>
>
Hi Rafał ,
The git push service was busy at that time and the branch
has been uploaded to github at 2020-11-14 03:22:56 +0800.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2020-11-16 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 9:50 [PATCH] ARM: dts: BCM5301X: Enable USB 3 PHY on Luxul XWR-3150 Rafał Miłecki
2020-11-13 13:41 ` kernel test robot
2020-11-13 13:51 ` Rafał Miłecki
2020-11-16 6:14 ` Rong Chen [this message]
2020-11-13 23:12 ` Florian Fainelli
2020-11-13 23:17 ` Florian Fainelli
2020-11-13 23:18 ` Rafał Miłecki
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=93f6e8ad-be48-76f3-ada7-dcb72fc9abaf@intel.com \
--to=rong.a.chen@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=rafal@milecki.pl \
--cc=zajec5@gmail.com \
/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).