public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: kbuild-all@01.org, Alexander Viro <viro@zeniv.linux.org.uk>,
	Jan Kara <jack@suse.com>, Jeff Layton <jlayton@poochiereds.net>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Tejun Heo <tj@kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Andi Kleen <andi@firstfloor.org>,
	Dave Chinner <dchinner@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Scott J Norton <scott.norton@hpe.com>,
	Douglas Hatch <doug.hatch@hpe.com>,
	Waiman Long <Waiman.Long@hpe.com>
Subject: Re: [PATCH v5 5/5] lib/dlock-list: Make sibling CPUs share the same linked list
Date: Wed, 10 Aug 2016 02:23:10 +0800	[thread overview]
Message-ID: <201608100243.zu4sjVF8%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470761563-25173-6-git-send-email-Waiman.Long@hpe.com>

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

Hi Waiman,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc1 next-20160809]
[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/Waiman-Long/vfs-Use-dlock-list-for-SB-s-s_inodes-list/20160810-012457
config: i386-randconfig-s0-201632 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All error/warnings (new ones prefixed by >>):

   lib/dlock-list.c: In function 'cpu2list_init':
>> lib/dlock-list.c:60:15: error: assignment to expression with array type
     sibling_mask = topology_sibling_cpumask(0);
                  ^
>> lib/dlock-list.c:61:6: warning: the address of 'sibling_mask' will always evaluate as 'true' [-Waddress]
     if (!sibling_mask)
         ^
   lib/dlock-list.c:74:16: error: assignment to expression with array type
      sibling_mask = topology_sibling_cpumask(cpu);
                   ^

vim +60 lib/dlock-list.c

    54		cpumask_var_t sibling_mask;
    55		static struct cpumask mask __initdata;
    56	
    57		/*
    58		 * Check # of sibling CPUs for CPU 0
    59		 */
  > 60		sibling_mask = topology_sibling_cpumask(0);
  > 61		if (!sibling_mask)
    62			goto done;
    63		nr_siblings = cpumask_weight(sibling_mask);
    64		if (nr_siblings == 1)

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

  reply	other threads:[~2016-08-09 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 16:52 [PATCH v5 0/5] vfs: Use dlock list for SB's s_inodes list Waiman Long
2016-08-09 16:52 ` [PATCH v5 1/5] lib/dlock-list: Distributed and lock-protected lists Waiman Long
2016-08-09 16:52 ` [PATCH v5 2/5] fsnotify: Simplify inode iteration on umount Waiman Long
2016-08-09 16:52 ` [PATCH v5 3/5] vfs: Remove unnecessary list_for_each_entry_safe() variants Waiman Long
2016-08-09 16:52 ` [PATCH v5 4/5] vfs: Use dlock list for superblock's inode list Waiman Long
2016-08-09 16:52 ` [PATCH v5 5/5] lib/dlock-list: Make sibling CPUs share the same linked list Waiman Long
2016-08-09 18:23   ` kbuild test robot [this message]
2016-08-09 19:46     ` Waiman Long
2016-08-09 18:44   ` kbuild test robot
2016-08-09 19:00   ` 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=201608100243.zu4sjVF8%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Waiman.Long@hpe.com \
    --cc=andi@firstfloor.org \
    --cc=bfields@fieldses.org \
    --cc=boqun.feng@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=dchinner@redhat.com \
    --cc=doug.hatch@hpe.com \
    --cc=jack@suse.com \
    --cc=jlayton@poochiereds.net \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=scott.norton@hpe.com \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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