public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <oe-kbuild-all@lists.linux.dev>,
	David Hildenbrand <david@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	<mm-commits@vger.kernel.org>, Davidlohr Bueso <dave@stgolabs.net>
Subject: [akpm-mm:mm-new 117/130] ./include/asm-generic/fixmap.h:77:9: error: implicit declaration of function '__set_fixmap'; did you mean 'set_fixmap'?
Date: Mon, 27 Apr 2026 22:45:39 +0800	[thread overview]
Message-ID: <ae92kz3LeyaFBvKw@rli9-mobl> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head:   4f7b2cc1ad8719d55a8de9675a0aca65cb17c364
commit: 93580c23bb3da5dd2926d6ae991ef04c2cdacaf2 [117/130] include/asm-generic/fixmap.h: reimplement nasty macros in C
config: powerpc64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260427/202604271114.ebmzs1LE-lkp@intel.com/config)
compiler: powerpc64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260427/202604271114.ebmzs1LE-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/r/202604271114.ebmzs1LE-lkp@intel.com/

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

   In file included from ./arch/powerpc/include/asm/fixmap.h:91,
                    from mm/early_ioremap.c:18:
   ./include/asm-generic/fixmap.h: In function '__set_fixmap_offset':
>> ./include/asm-generic/fixmap.h:77:9: error: implicit declaration of function '__set_fixmap'; did you mean 'set_fixmap'? [-Wimplicit-function-declaration]
      77 |         __set_fixmap(idx, phys, flags);
         |         ^~~~~~~~~~~~
         |         set_fixmap
   ./arch/powerpc/include/asm/fixmap.h: At top level:
>> ./arch/powerpc/include/asm/fixmap.h:93:20: warning: conflicting types for '__set_fixmap'; have 'void(enum fixed_addresses,  phys_addr_t,  pgprot_t)' {aka 'void(enum fixed_addresses,  long long unsigned int,  pgprot_t)'}
      93 | static inline void __set_fixmap(enum fixed_addresses idx,
         |                    ^~~~~~~~~~~~
>> ./arch/powerpc/include/asm/fixmap.h:93:20: error: static declaration of '__set_fixmap' follows non-static declaration
   ./include/asm-generic/fixmap.h:77:9: note: previous implicit declaration of '__set_fixmap' with type 'void(enum fixed_addresses,  phys_addr_t,  pgprot_t)' {aka 'void(enum fixed_addresses,  long long unsigned int,  pgprot_t)'}
      77 |         __set_fixmap(idx, phys, flags);
         |         ^~~~~~~~~~~~


vim +77 ./include/asm-generic/fixmap.h

d57c33c5daa4ef Mark Salter   2014-01-23  72  
d57c33c5daa4ef Mark Salter   2014-01-23  73  /* Return a pointer with offset calculated */
93580c23bb3da5 Andrew Morton 2026-04-25  74  static inline unsigned long
93580c23bb3da5 Andrew Morton 2026-04-25  75  __set_fixmap_offset(enum fixed_addresses idx, phys_addr_t phys, pgprot_t flags)
93580c23bb3da5 Andrew Morton 2026-04-25  76  {
93580c23bb3da5 Andrew Morton 2026-04-25 @77  	__set_fixmap(idx, phys, flags);
93580c23bb3da5 Andrew Morton 2026-04-25  78  	return fix_to_virt(idx) + (phys & (PAGE_SIZE - 1));
93580c23bb3da5 Andrew Morton 2026-04-25  79  }
d57c33c5daa4ef Mark Salter   2014-01-23  80  

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



             reply	other threads:[~2026-04-27 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 14:45 kernel test robot [this message]
2026-04-27 14:55 ` [akpm-mm:mm-new 117/130] ./include/asm-generic/fixmap.h:77:9: error: implicit declaration of function '__set_fixmap'; did you mean 'set_fixmap'? Andrew Morton

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=ae92kz3LeyaFBvKw@rli9-mobl \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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