From: Baoquan He <bhe@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: "Brijesh Singh" <brijesh.singh@amd.com>,
devicetree@vger.kernel.org, "David Airlie" <airlied@linux.ie>,
linux-pci@vger.kernel.org, "Wei Yang" <richard.weiyang@gmail.com>,
"Keith Busch" <keith.busch@intel.com>,
"Yaowei Bai" <baiyaowei@cmss.chinamobile.com>,
"Frank Rowand" <frowand.list@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
linux-nvdimm@lists.01.org,
"Patrik Jakobsson" <patrik.r.jakobsson@gmail.com>,
linux-input@vger.kernel.org, "Borislav Petkov" <bp@suse.de>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Jonathan Derrick" <jonathan.derrick@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, kbuild-all@01.org,
devel@linuxdriverproject.org
Subject: Re: [PATCH v2 1/3] resource: Use list_head to link sibling resource
Date: Sun, 8 Apr 2018 17:09:03 +0800 [thread overview]
Message-ID: <20180408090903.GE19345@localhost.localdomain> (raw)
In-Reply-To: <201804081247.F3eqBMih%fengguang.wu@intel.com>
Hi,
Thanks for telling!
On 04/08/18 at 12:12pm, 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.16 next-20180406]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Baoquan-He/resource-Use-list_head-to-link-sibling-resource/20180408-110108
> config: parisc-c3000_defconfig (attached as .config)
> compiler: hppa-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
> make.cross ARCH=parisc
>
> All errors (new ones prefixed by >>):
>
> drivers//parisc/lba_pci.c: In function 'lba_dump_res':
> >> drivers//parisc/lba_pci.c:173:15: error: incompatible type for argument 1 of 'lba_dump_res'
> lba_dump_res(r->child, d+2);
I compiled with allyesconfig, don't know why this was missed. Will
change and repost.
> ^
> drivers//parisc/lba_pci.c:162:1: note: expected 'struct resource *' but argument is of type 'struct list_head'
> lba_dump_res(struct resource *r, int d)
> ^~~~~~~~~~~~
> drivers//parisc/lba_pci.c:174:15: error: incompatible type for argument 1 of 'lba_dump_res'
> lba_dump_res(r->sibling, d);
> ^
> drivers//parisc/lba_pci.c:162:1: note: expected 'struct resource *' but argument is of type 'struct list_head'
> lba_dump_res(struct resource *r, int d)
> ^~~~~~~~~~~~
>
> vim +/lba_dump_res +173 drivers//parisc/lba_pci.c
>
> ^1da177e Linus Torvalds 2005-04-16 159
> ^1da177e Linus Torvalds 2005-04-16 160
> ^1da177e Linus Torvalds 2005-04-16 161 static void
> ^1da177e Linus Torvalds 2005-04-16 162 lba_dump_res(struct resource *r, int d)
> ^1da177e Linus Torvalds 2005-04-16 163 {
> ^1da177e Linus Torvalds 2005-04-16 164 int i;
> ^1da177e Linus Torvalds 2005-04-16 165
> ^1da177e Linus Torvalds 2005-04-16 166 if (NULL == r)
> ^1da177e Linus Torvalds 2005-04-16 167 return;
> ^1da177e Linus Torvalds 2005-04-16 168
> ^1da177e Linus Torvalds 2005-04-16 169 printk(KERN_DEBUG "(%p)", r->parent);
> ^1da177e Linus Torvalds 2005-04-16 170 for (i = d; i ; --i) printk(" ");
> 645d11d4 Matthew Wilcox 2006-12-24 171 printk(KERN_DEBUG "%p [%lx,%lx]/%lx\n", r,
> 645d11d4 Matthew Wilcox 2006-12-24 172 (long)r->start, (long)r->end, r->flags);
> ^1da177e Linus Torvalds 2005-04-16 @173 lba_dump_res(r->child, d+2);
> ^1da177e Linus Torvalds 2005-04-16 174 lba_dump_res(r->sibling, d);
> ^1da177e Linus Torvalds 2005-04-16 175 }
> ^1da177e Linus Torvalds 2005-04-16 176
>
> :::::: The code at line 173 was first introduced by commit
> :::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
>
> :::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
> :::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-04-08 9:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 2:47 [PATCH v2 0/3] resource: Use list_head to link sibling resource Baoquan He
2018-04-08 2:47 ` [PATCH v2 1/3] " Baoquan He
2018-04-08 4:12 ` kbuild test robot
2018-04-08 9:09 ` Baoquan He [this message]
2018-04-08 5:55 ` kbuild test robot
2018-04-08 9:09 ` Baoquan He
2018-04-09 9:08 ` [PATCH v3 1/3] resource: Use list_head to link resource sibling Baoquan He
2018-04-09 14:49 ` Rob Herring
2018-04-09 16:05 ` Nicolas Pitre
2018-04-10 13:44 ` Baoquan He
2018-04-11 3:22 ` Wei Yang
2018-04-09 15:38 ` Dan Williams
2018-04-10 2:10 ` Baoquan He
2018-04-10 2:34 ` Dan Williams
2018-04-10 2:49 ` Baoquan He
2018-04-08 2:47 ` [PATCH v2 2/3] resource: add walk_system_ram_res_rev() Baoquan He
2018-04-08 2:47 ` [PATCH v2 3/3] 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=20180408090903.GE19345@localhost.localdomain \
--to=bhe@redhat.com \
--cc=airlied@linux.ie \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=dan.j.williams@intel.com \
--cc=devel@linuxdriverproject.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jglisse@redhat.com \
--cc=jonathan.derrick@intel.com \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=patrik.r.jakobsson@gmail.com \
--cc=richard.weiyang@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.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).