From: Baoquan He <bhe@redhat•com>
To: kbuild test robot <lkp@intel•com>
Cc: kbuild-all@01•org, linux-kernel@vger•kernel.org,
akpm@linux-foundation•org, robh+dt@kernel•org,
dan.j.williams@intel•com, nicolas.pitre@linaro•org,
josh@joshtriplett•org, fengguang.wu@intel•com, bp@suse•de,
andy.shevchenko@gmail•com, brijesh.singh@amd•com,
devicetree@vger•kernel.org, airlied@linux•ie,
linux-pci@vger•kernel.org, richard.weiyang@gmail•com,
keith.busch@intel•com, jcmvbkbc@gmail•com,
baiyaowei@cmss•chinamobile.com, frowand.list@gmail•com,
lorenzo.pieralisi@arm•com, sthemmin@microsoft•com,
linux-nvdimm@lists•01.org, patrik.r.jakobsson@gmail•com,
linux-input@vger•kernel.org, gustavo@padovan•org,
dyoung@redhat•com, vgoyal@redhat•com, thomas.lendacky@amd•com,
haiyangz@microsoft•com, maarten.lankhorst@linux•intel.com,
jglisse@redhat•com, seanpaul@chromium•org, bhelgaas@google•com,
tglx@linutronix•de, yinghai@kernel•org,
jonathan.derrick@intel•com, chris@zankel•net, monstr@monstr•eu,
linux-parisc@vger•kernel.org, gregkh@linuxfoundation•org,
dmitry.torokhov@gmail•com, kexec@lists•infradead.org,
ebiederm@xmission•com, devel@linuxdriverproject•org,
linuxppc-dev@lists•ozlabs.org, davem@davemloft•net
Subject: Re: [PATCH v6 2/4] resource: Use list_head to link sibling resource
Date: Sun, 8 Jul 2018 10:59:46 +0800 [thread overview]
Message-ID: <20180708025946.GI3047@MiWiFi-R3L-srv> (raw)
In-Reply-To: <201807042347.hfDcKxmG%fengguang.wu@intel.com>
Hi,
On 07/05/18 at 01:00am, kbuild test robot wrote:
> Hi Baoquan,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.18-rc3 next-20180704]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
Thanks for telling.
I cloned 0day-ci/linut to my local pc.
https://github.com/0day-ci/linux.git
However, I didn't find below branch. And tried to open it in web
broswer, also failed.
> url: https://github.com/0day-ci/linux/commits/Baoquan-He/resource-Use-list_head-to-link-sibling-resource/20180704-121402
> config: mips-rb532_defconfig (attached as .config)
> compiler: mipsel-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> GCC_VERSION=7.2.0 make.cross ARCH=mips
I did find a old one which is for the old version 5 post.
[bhe@linux]$ git remote -v
0day-ci https://github.com/0day-ci/linux.git (fetch)
0day-ci https://github.com/0day-ci/linux.git (push)
[bhe@dhcp-128-28 linux]$ git branch -a| grep Baoquan| grep resource
remotes/0day-ci/Baoquan-He/resource-Use-list_head-to-link-sibling-resource/20180612-113600
Could you help have a look at this?
Thanks
Baoquan
>
> All error/warnings (new ones prefixed by >>):
>
> >> arch/mips/pci/pci-rc32434.c:57:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> .child = &rc32434_res_pci_mem2
> ^
> arch/mips/pci/pci-rc32434.c:57:11: note: (near initialization for 'rc32434_res_pci_mem1.child.next')
> >> arch/mips/pci/pci-rc32434.c:51:47: warning: missing braces around initializer [-Wmissing-braces]
> static struct resource rc32434_res_pci_mem1 = {
> ^
> arch/mips/pci/pci-rc32434.c:60:47: warning: missing braces around initializer [-Wmissing-braces]
> static struct resource rc32434_res_pci_mem2 = {
> ^
> cc1: some warnings being treated as errors
>
> vim +57 arch/mips/pci/pci-rc32434.c
>
> 73b4390f Ralf Baechle 2008-07-16 50
> 73b4390f Ralf Baechle 2008-07-16 @51 static struct resource rc32434_res_pci_mem1 = {
> 73b4390f Ralf Baechle 2008-07-16 52 .name = "PCI MEM1",
> 73b4390f Ralf Baechle 2008-07-16 53 .start = 0x50000000,
> 73b4390f Ralf Baechle 2008-07-16 54 .end = 0x5FFFFFFF,
> 73b4390f Ralf Baechle 2008-07-16 55 .flags = IORESOURCE_MEM,
> 73b4390f Ralf Baechle 2008-07-16 56 .sibling = NULL,
> 73b4390f Ralf Baechle 2008-07-16 @57 .child = &rc32434_res_pci_mem2
> 73b4390f Ralf Baechle 2008-07-16 58 };
> 73b4390f Ralf Baechle 2008-07-16 59
>
> :::::: The code at line 57 was first introduced by commit
> :::::: 73b4390fb23456964201abda79f1210fe337d01a [MIPS] Routerboard 532: Support for base system
>
> :::::: TO: Ralf Baechle <ralf@linux-mips•org>
> :::::: CC: Ralf Baechle <ralf@linux-mips•org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-07-08 3:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 4:10 [PATCH v6 0/4] resource: Use list_head to link sibling resource Baoquan He
2018-07-04 4:10 ` [PATCH v6 1/4] resource: Move reparent_resources() to kernel/resource.c and make it public Baoquan He
2018-07-04 16:46 ` Andy Shevchenko
2018-07-05 10:09 ` Baoquan He
2018-07-04 4:10 ` [PATCH v6 2/4] resource: Use list_head to link sibling resource Baoquan He
2018-07-04 17:00 ` kbuild test robot
2018-07-04 17:00 ` kbuild test robot
2018-07-08 2:59 ` Baoquan He [this message]
2018-07-08 17:48 ` Andy Shevchenko
2018-07-09 3:04 ` Baoquan He
2018-07-10 0:59 ` [kbuild-all] " Ye Xiaolong
2018-07-10 3:10 ` Baoquan He
2018-07-04 4:10 ` [PATCH v6 3/4] resource: add walk_system_ram_res_rev() Baoquan He
2018-07-04 4:10 ` [PATCH v6 4/4] kexec_file: Load kernel at top of system RAM if required Baoquan He
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=20180708025946.GI3047@MiWiFi-R3L-srv \
--to=bhe@redhat$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=baiyaowei@cmss$(echo .)chinamobile.com \
--cc=bhelgaas@google$(echo .)com \
--cc=bp@suse$(echo .)de \
--cc=brijesh.singh@amd$(echo .)com \
--cc=chris@zankel$(echo .)net \
--cc=dan.j.williams@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=devel@linuxdriverproject$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=dyoung@redhat$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=fengguang.wu@intel$(echo .)com \
--cc=frowand.list@gmail$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=gustavo@padovan$(echo .)org \
--cc=haiyangz@microsoft$(echo .)com \
--cc=jcmvbkbc@gmail$(echo .)com \
--cc=jglisse@redhat$(echo .)com \
--cc=jonathan.derrick@intel$(echo .)com \
--cc=josh@joshtriplett$(echo .)org \
--cc=kbuild-all@01$(echo .)org \
--cc=keith.busch@intel$(echo .)com \
--cc=kexec@lists$(echo .)infradead.org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-nvdimm@lists$(echo .)01.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lkp@intel$(echo .)com \
--cc=lorenzo.pieralisi@arm$(echo .)com \
--cc=maarten.lankhorst@linux$(echo .)intel.com \
--cc=monstr@monstr$(echo .)eu \
--cc=nicolas.pitre@linaro$(echo .)org \
--cc=patrik.r.jakobsson@gmail$(echo .)com \
--cc=richard.weiyang@gmail$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=seanpaul@chromium$(echo .)org \
--cc=sthemmin@microsoft$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=thomas.lendacky@amd$(echo .)com \
--cc=vgoyal@redhat$(echo .)com \
--cc=yinghai@kernel$(echo .)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