linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Yury Norov <yury.norov@gmail.com>
Subject: [linux-next:master 8187/8914] lib/bitmap.c:351:6: error: conflicting types for '__bitmap_set'
Date: Fri, 8 Jul 2022 21:13:11 +0800	[thread overview]
Message-ID: <202207082141.JR9ENDa5-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f2528c29385819a84480cacef4886b049761e2c5
commit: aaa4ab5ec04480fd0c16c7452d28444c862b2b87 [8187/8914] lib/bitmap: Make length parameter `len` unsigned
config: x86_64-randconfig-a016 (https://download.01.org/0day-ci/archive/20220708/202207082141.JR9ENDa5-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 562c3467a6738aa89203f72fc1d1343e5baadf3c)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=aaa4ab5ec04480fd0c16c7452d28444c862b2b87
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout aaa4ab5ec04480fd0c16c7452d28444c862b2b87
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-next/master HEAD f2528c29385819a84480cacef4886b049761e2c5 builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

>> lib/bitmap.c:351:6: error: conflicting types for '__bitmap_set'
   void __bitmap_set(unsigned long *map, unsigned int start, unsigned int len)
        ^
   include/linux/bitmap.h:167:6: note: previous declaration is here
   void __bitmap_set(unsigned long *map, unsigned int start, int len);
        ^
   1 error generated.


vim +/__bitmap_set +351 lib/bitmap.c

   350	
 > 351	void __bitmap_set(unsigned long *map, unsigned int start, unsigned int len)
   352	{
   353		unsigned long *p = map + BIT_WORD(start);
   354		const unsigned int size = start + len;
   355		int bits_to_set = BITS_PER_LONG - (start % BITS_PER_LONG);
   356		unsigned long mask_to_set = BITMAP_FIRST_WORD_MASK(start);
   357	
   358		while (len >= bits_to_set) {
   359			*p |= mask_to_set;
   360			len -= bits_to_set;
   361			bits_to_set = BITS_PER_LONG;
   362			mask_to_set = ~0UL;
   363			p++;
   364		}
   365		if (len) {
   366			mask_to_set &= BITMAP_LAST_WORD_MASK(size);
   367			*p |= mask_to_set;
   368		}
   369	}
   370	EXPORT_SYMBOL(__bitmap_set);
   371	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-07-08 13:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202207082141.JR9ENDa5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=pmenzel@molgen.mpg.de \
    --cc=yury.norov@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).