mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chen Yucong <slaoub@gmail.com>
Cc: kbuild-all@01.org, mingo@kernel.org, tglx@linutronix.de,
	hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/kernel: use pr_<level>() and dev_<level>
Date: Sun, 14 Feb 2016 13:07:09 +0800	[thread overview]
Message-ID: <201602141301.fXA1nSag%fengguang.wu@intel.com> (raw)
In-Reply-To: <1455423047-8571-1-git-send-email-slaoub@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]

Hi Chen,

[auto build test WARNING on tip/x86/core]
[also build test WARNING on v4.5-rc3 next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Chen-Yucong/x86-kernel-use-pr_-level-and-dev_-level/20160214-121236
config: x86_64-allmodconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> arch/x86/pci/mmconfig_64.c:16:0: warning: "pr_fmt" redefined
    #define pr_fmt(fmt) "PCI: " fmt
    ^
   In file included from include/linux/kernel.h:13:0,
                    from include/linux/list.h:8,
                    from include/linux/pci.h:25,
                    from arch/x86/pci/mmconfig_64.c:8:
   include/linux/printk.h:236:0: note: this is the location of the previous definition
    #define pr_fmt(fmt) fmt
    ^

vim +/pr_fmt +16 arch/x86/pci/mmconfig_64.c

     1	/*
     2	 * mmconfig.c - Low-level direct PCI config space access via MMCONFIG
     3	 *
     4	 * This is an 64bit optimized version that always keeps the full mmconfig
     5	 * space mapped. This allows lockless config space operation.
     6	 */
     7	
     8	#include <linux/pci.h>
     9	#include <linux/init.h>
    10	#include <linux/acpi.h>
    11	#include <linux/bitmap.h>
    12	#include <linux/rcupdate.h>
    13	#include <asm/e820.h>
    14	#include <asm/pci_x86.h>
    15	
  > 16	#define pr_fmt(fmt) "PCI: " fmt
    17	
    18	static char __iomem *pci_dev_base(unsigned int seg, unsigned int bus, unsigned int devfn)
    19	{
    20		struct pci_mmcfg_region *cfg = pci_mmconfig_lookup(seg, bus);
    21	
    22		if (cfg && cfg->virt)
    23			return cfg->virt + (PCI_MMCFG_BUS_OFFSET(bus) | (devfn << 12));
    24		return NULL;

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 53128 bytes --]

  parent reply	other threads:[~2016-02-14  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  4:10 Chen Yucong
2016-02-14  4:22 ` kbuild test robot
2016-02-14  5:07 ` kbuild test robot [this message]
2016-02-14 14:08 ` Borislav Petkov
2016-02-16  8:24   ` Ingo Molnar
2016-02-16  9:01     ` Borislav Petkov

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=201602141301.fXA1nSag%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=slaoub@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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®