devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, bhelgaas@google.com
Subject: Re: [PATCH next 1/2] PCI: keystone: add pci error irq handler
Date: Thu, 24 Mar 2016 17:36:59 -0400	[thread overview]
Message-ID: <56F45DFB.7030408@ti.com> (raw)
In-Reply-To: <201603230621.h4pXMyFx%fengguang.wu@intel.com>

On 03/22/2016 06:23 PM, kbuild test robot wrote:
> Hi Murali,
> 
> [auto build test ERROR on next-20160322]
> 
> url:    https://github.com/0day-ci/linux/commits/Murali-Karicheri/PCI-keystone-add-pci-error-irq-handler/20160323-035516
> config: arm-multi_v7_defconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=arm 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/pci/host/pci-keystone.c: In function 'ks_pcie_probe':
>>> drivers/pci/host/pci-keystone.c:410:16: error: 'node' undeclared (first use in this function)
>      ks_pcie->np = node;
>                    ^
>    drivers/pci/host/pci-keystone.c:410:16: note: each undeclared identifier is reported only once for each function it appears in
> 
> vim +/node +410 drivers/pci/host/pci-keystone.c
> 
>    404			return PTR_ERR(reg_p);
>    405		ks_pcie->device_id = readl(reg_p) >> 16;
>    406		devm_iounmap(dev, reg_p);
>    407		devm_release_mem_region(dev, res->start, resource_size(res));
>    408	
>    409		pp->dev = dev;
>  > 410		ks_pcie->np = node;
>    411		platform_set_drvdata(pdev, ks_pcie);
>    412		ks_pcie->clk = devm_clk_get(dev, "pcie");
>    413		if (IS_ERR(ks_pcie->clk)) {
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> 
I don't anything obvious to cause this failure. It builds from arm-pci with these patches applied
and I have tried multi_v7_defconfig for arm as well. I will follow the instructions here and
check if I can reproduce this and post a updated a patch.

-- 
Murali Karicheri
Linux Kernel, Keystone

  reply	other threads:[~2016-03-24 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 19:52 [PATCH next 1/2] PCI: keystone: add pci error irq handler Murali Karicheri
     [not found] ` <1458676378-24377-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2016-03-22 19:52   ` [PATCH next 2/2] PCI: keystone: remove unnecessary goto statement Murali Karicheri
2016-03-22 22:23 ` [PATCH next 1/2] PCI: keystone: add pci error irq handler kbuild test robot
2016-03-24 21:36   ` Murali Karicheri [this message]
2016-04-06 17:11   ` Murali Karicheri
2016-03-23 15:10 ` Rob Herring
2016-03-31 22:11 ` Murali Karicheri

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=56F45DFB.7030408@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.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).