mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: kbuild-all@01.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] pci: Update VPD size with correct length
Date: Fri, 23 Oct 2015 18:47:46 +0800	[thread overview]
Message-ID: <201510231810.RlZ52VfY%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445591396-95395-1-git-send-email-hare@suse.de>

Hi Hannes,

[auto build test WARNING on pci/next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Hannes-Reinecke/pci-Update-VPD-size-with-correct-length/20151023-171224
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/pci/access.c:499:1: sparse: symbol 'pci_vpd_pci22_size' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

       reply	other threads:[~2015-10-23 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 10:47 kbuild test robot [this message]
2015-10-23  9:09 ` Hannes Reinecke
2015-10-23 10:47   ` [RFC PATCH] pci: pci_vpd_pci22_size can be static kbuild test robot
2015-10-24  0:52   ` [PATCH] pci: Update VPD size with correct length Alexander Duyck
2015-10-25  3:34     ` Hannes Reinecke
2015-11-25 17:17       ` Bjorn Helgaas
2015-11-25 18:01         ` Alexander Duyck
2015-12-16 10:28 Hannes Reinecke
2015-12-16 10:41 ` kbuild test robot

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=201510231810.RlZ52VfY%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bhelgaas@google.com \
    --cc=hare@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®