All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 2523/3504] arch/parisc/include/asm/cmpxchg.h:75:24: error: implicit declaration of function 'cmpxchg_emu_u16'
Date: Thu, 4 Apr 2024 09:38:22 +0800	[thread overview]
Message-ID: <202404040944.CqvTiLwp-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   727900b675b749c40ba1f6669c7ae5eb7eb8e837
commit: 2f6e60c348365df92f431f9101f7fa8f29c7a178 [2523/3504] parisc: Emulate two-byte cmpxchg
config: parisc-randconfig-r036-20230421 (https://download.01.org/0day-ci/archive/20240404/202404040944.CqvTiLwp-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240404/202404040944.CqvTiLwp-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404040944.CqvTiLwp-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/parisc/include/asm/atomic.h:10,
                    from include/linux/atomic.h:7,
                    from arch/parisc/include/asm/bitops.h:13,
                    from include/linux/bitops.h:68,
                    from include/linux/kernel.h:23,
                    from arch/parisc/include/asm/bug.h:5,
                    from include/linux/bug.h:5,
                    from include/linux/page-flags.h:10,
                    from kernel/bounds.c:10:
   arch/parisc/include/asm/cmpxchg.h: In function '__cmpxchg':
>> arch/parisc/include/asm/cmpxchg.h:75:24: error: implicit declaration of function 'cmpxchg_emu_u16' [-Werror=implicit-function-declaration]
      75 |         case 2: return cmpxchg_emu_u16((volatile u16 *)ptr, old, new);
         |                        ^~~~~~~~~~~~~~~
>> arch/parisc/include/asm/cmpxchg.h:75:66: error: 'new' undeclared (first use in this function); did you mean 'new_'?
      75 |         case 2: return cmpxchg_emu_u16((volatile u16 *)ptr, old, new);
         |                                                                  ^~~
         |                                                                  new_
   arch/parisc/include/asm/cmpxchg.h:75:66: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors
   make[3]: *** [scripts/Makefile.build:117: kernel/bounds.s] Error 1
   make[3]: Target 'prepare' not remade because of errors.
   make[2]: *** [Makefile:1197: prepare0] Error 2
   make[2]: Target 'prepare' not remade because of errors.
   make[1]: *** [Makefile:240: __sub-make] Error 2
   make[1]: Target 'prepare' not remade because of errors.
   make: *** [Makefile:240: __sub-make] Error 2
   make: Target 'prepare' not remade because of errors.


vim +/cmpxchg_emu_u16 +75 arch/parisc/include/asm/cmpxchg.h

    64	
    65	/* don't worry...optimizer will get rid of most of this */
    66	static inline unsigned long
    67	__cmpxchg(volatile void *ptr, unsigned long old, unsigned long new_, int size)
    68	{
    69		switch (size) {
    70	#ifdef CONFIG_64BIT
    71		case 8: return __cmpxchg_u64((u64 *)ptr, old, new_);
    72	#endif
    73		case 4: return __cmpxchg_u32((unsigned int *)ptr,
    74					     (unsigned int)old, (unsigned int)new_);
  > 75		case 2: return cmpxchg_emu_u16((volatile u16 *)ptr, old, new);
    76		case 1: return __cmpxchg_u8((u8 *)ptr, old & 0xff, new_ & 0xff);
    77		}
    78		__cmpxchg_called_with_bad_pointer();
    79		return old;
    80	}
    81	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-04-04  1:39 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=202404040944.CqvTiLwp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paulmck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.