mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	David Vrabel <david.vrabel@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Julien Grall <julien.grall@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Ross Lagerwall <ross.lagerwall@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/events: use virt_xxx barriers
Date: Mon, 4 Jan 2016 19:56:36 +0800	[thread overview]
Message-ID: <201601041909.zLSDZK5R%fengguang.wu@intel.com> (raw)
In-Reply-To: <1451907925-15768-1-git-send-email-mst@redhat.com>

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

Hi Michael,

[auto build test ERROR on v4.4-rc8]
[also build test ERROR on next-20151231]
[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/Michael-S-Tsirkin/xen-events-use-virt_xxx-barriers/20160104-194916
config: x86_64-randconfig-x008-01040711 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/xen/events/events_fifo.c: In function 'consume_one_event':
>> drivers/xen/events/events_fifo.c:300:3: error: implicit declaration of function 'virt_rmb' [-Werror=implicit-function-declaration]
      virt_rmb(); /* Ensure word is up-to-date before reading head. */
      ^
   cc1: some warnings being treated as errors

vim +/virt_rmb +300 drivers/xen/events/events_fifo.c

   294	
   295		/*
   296		 * Reached the tail last time?  Read the new HEAD from the
   297		 * control block.
   298		 */
   299		if (head == 0) {
 > 300			virt_rmb(); /* Ensure word is up-to-date before reading head. */
   301			head = control_block->head[priority];
   302		}
   303	

---
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: 21830 bytes --]

      parent reply	other threads:[~2016-01-04 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 11:46 Michael S. Tsirkin
2016-01-04 11:47 ` David Vrabel
2016-01-04 11:56 ` kbuild test robot [this message]

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=201601041909.zLSDZK5R%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=kbuild-all@01.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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®