All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-nonmm-unstable 43/43] arch/powerpc/kernel/nvram_64.c:79:10: error: incompatible function pointer types initializing 'void (*)(struct kmsg_dumper *, enum kmsg_dump_reason, const char *)' with an expression of type 'void (struct kmsg_dumper *, enum kmsg_dump_reason)'
Date: Thu, 27 Jun 2024 00:37:23 +0800	[thread overview]
Message-ID: <202406270010.IIwJCerE-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head:   7e72bb7504d1192ab89809f6192dba1b06f4fa51
commit: 7e72bb7504d1192ab89809f6192dba1b06f4fa51 [43/43] printk: add a short description string to kmsg_dump()
config: powerpc64-randconfig-002-20240626 (https://download.01.org/0day-ci/archive/20240627/202406270010.IIwJCerE-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240627/202406270010.IIwJCerE-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/202406270010.IIwJCerE-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/powerpc/kernel/nvram_64.c:79:10: error: incompatible function pointer types initializing 'void (*)(struct kmsg_dumper *, enum kmsg_dump_reason, const char *)' with an expression of type 'void (struct kmsg_dumper *, enum kmsg_dump_reason)' [-Werror,-Wincompatible-function-pointer-types]
           .dump = oops_to_nvram
                   ^~~~~~~~~~~~~
>> arch/powerpc/kernel/nvram_64.c:645:13: error: conflicting types for 'oops_to_nvram'
   static void oops_to_nvram(struct kmsg_dumper *dumper,
               ^
   arch/powerpc/kernel/nvram_64.c:75:13: note: previous declaration is here
   static void oops_to_nvram(struct kmsg_dumper *dumper,
               ^
   2 errors generated.


vim +79 arch/powerpc/kernel/nvram_64.c

78989f0a559218 Hari Bathini 2015-02-06  74  
78989f0a559218 Hari Bathini 2015-02-06  75  static void oops_to_nvram(struct kmsg_dumper *dumper,
78989f0a559218 Hari Bathini 2015-02-06  76  			  enum kmsg_dump_reason reason);
78989f0a559218 Hari Bathini 2015-02-06  77  
78989f0a559218 Hari Bathini 2015-02-06  78  static struct kmsg_dumper nvram_kmsg_dumper = {
78989f0a559218 Hari Bathini 2015-02-06 @79  	.dump = oops_to_nvram
78989f0a559218 Hari Bathini 2015-02-06  80  };
78989f0a559218 Hari Bathini 2015-02-06  81  

:::::: The code at line 79 was first introduced by commit
:::::: 78989f0a5592182a3d45d869ddaafc71c8f673af powerpc/nvram: Move generic code for nvram and pstore

:::::: TO: Hari Bathini <hbathini@linux.vnet.ibm.com>
:::::: CC: Michael Ellerman <mpe@ellerman.id.au>

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

                 reply	other threads:[~2024-06-26 16:38 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=202406270010.IIwJCerE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=jfalempe@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --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 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.