LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: kbuild-all@01.org, linus.walleij@linaro.org,
	linux-gpio@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	William Breathitt Gray <vilhelm.gray@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/7] bitops: Introduce the for_each_set_port_word macro
Date: Tue, 8 May 2018 07:36:31 +0800	[thread overview]
Message-ID: <201805080517.QN2WX3Iy%fengguang.wu@intel.com> (raw)
In-Reply-To: <7b704b1feb2f2cdb6c3a3061fa5f5d804954d15d.1525704095.git.vilhelm.gray@gmail.com>

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

Hi William,

I love your patch! Yet something to improve:

[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.17-rc4 next-20180507]
[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/William-Breathitt-Gray/Introduce-the-for_each_set_port_word-macro/20180508-034417
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: openrisc-or1ksim_defconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 6.0.0 20160327 (experimental)
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=openrisc 

All errors (new ones prefixed by >>):

   In file included from arch/openrisc/include/asm/bitops.h:37:0,
                    from include/linux/bitops.h:38,
                    from include/linux/radix-tree.h:24,
                    from kernel/memremap.c:13:
>> include/asm-generic/bitops/find.h:98:1: error: unknown type name 'size_t'
    size_t find_next_port_word(size_t *const word_index,
    ^~~~~~
   include/asm-generic/bitops/find.h:98:28: error: unknown type name 'size_t'
    size_t find_next_port_word(size_t *const word_index,
                               ^~~~~~
   include/asm-generic/bitops/find.h:100:46: error: unknown type name 'size_t'
          const unsigned long *const bits, const size_t size,
                                                 ^~~~~~
   include/asm-generic/bitops/find.h:101:13: error: unknown type name 'size_t'
          const size_t offset, const unsigned int port_size);
                ^~~~~~

vim +/size_t +98 include/asm-generic/bitops/find.h

    82	
    83	/**
    84	 * find_next_port_word - find next port word with set bits in a memory region
    85	 * @word_index: location to store bitmap word index of found port word
    86	 * @word_offset: bits offset of the found port word in respective bitmap word
    87	 * @bits: address to base the search on
    88	 * @size: bitmap size in number of ports
    89	 * @offset: port word index to start searching at
    90	 * @port_size: port word size in bits
    91	 *
    92	 * Returns the port index for the next port word with set bits; the respective
    93	 * bitmap word index is stored at the location pointed by @word_index, and the
    94	 * bits offset of the found port word within the respective bitmap word is
    95	 * stored at the location pointed by @word_offset. If no bits are set, returns
    96	 * @size.
    97	 */
  > 98	size_t find_next_port_word(size_t *const word_index,
    99				   unsigned int *const word_offset,
   100				   const unsigned long *const bits, const size_t size,
   101				   const size_t offset, const unsigned int port_size);
   102	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7407 bytes --]

  reply	other threads:[~2018-05-07 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 15:35 [PATCH 0/7] " William Breathitt Gray
2018-05-07 15:35 ` [PATCH 1/7] bitops: " William Breathitt Gray
2018-05-07 23:36   ` kbuild test robot [this message]
2018-05-07 15:35 ` [PATCH 2/7] gpio: 104-dio-48e: Utilize " William Breathitt Gray
2018-05-07 15:35 ` [PATCH 3/7] gpio: 104-idi-48: " William Breathitt Gray
2018-05-07 15:36 ` [PATCH 4/7] gpio: gpio-mm: " William Breathitt Gray
2018-05-07 15:36 ` [PATCH 5/7] gpio: ws16c48: " William Breathitt Gray
2018-05-07 15:36 ` [PATCH 6/7] gpio: pci-idio-16: " William Breathitt Gray
2018-05-07 15:36 ` [PATCH 7/7] gpio: pcie-idio-24: " William Breathitt Gray

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=201805080517.QN2WX3Iy%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vilhelm.gray@gmail.com \
    --subject='Re: [PATCH 1/7] bitops: Introduce the for_each_set_port_word macro' \
    /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

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).