linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: "Steven, Price," <steven.price@arm.com>,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 11894/13554] arch/riscv/mm/ptdump.c:255:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int, int,  u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int,  int, long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int,  int,  long unsigned int)'
Date: Fri, 29 May 2020 11:22:12 -0700	[thread overview]
Message-ID: <20200529112212.42e84af2ba0f1030b33658dd@linux-foundation.org> (raw)
In-Reply-To: <202005300054.IITfkKUU%lkp@intel.com>

On Sat, 30 May 2020 00:14:57 +0800 kbuild test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   ff387fc20c697cdc887b2abf7ef494e853795a2f
> commit: f6396a9ececda3fa26571ccd38167373db1d2ec3 [11894/13554] mm: ptdump: expand type of 'val' in note_page()
> config: riscv-allyesconfig (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.0
> 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
>         git checkout f6396a9ececda3fa26571ccd38167373db1d2ec3
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
> arch/riscv/mm/ptdump.c: In function 'ptdump_walk':
> >> arch/riscv/mm/ptdump.c:255:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int,  int,  u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int,  int,  long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int,  int,  long unsigned int)' [-Werror=incompatible-pointer-types]
> 255 |    .note_page = note_page,

Thanks.

--- a/arch/riscv/mm/ptdump.c~mm-ptdump-expand-type-of-val-in-note_page-fix
+++ a/arch/riscv/mm/ptdump.c
@@ -204,7 +204,7 @@ static void note_prot_wx(struct pg_state
 }
 
 static void note_page(struct ptdump_state *pt_st, unsigned long addr,
-		      int level, unsigned long val)
+		      int level, u64 val)
 {
 	struct pg_state *st = container_of(pt_st, struct pg_state, ptdump);
 	u64 pa = PFN_PHYS(pte_pfn(__pte(val)));
_



      reply	other threads:[~2020-05-29 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 16:14 [linux-next:master 11894/13554] arch/riscv/mm/ptdump.c:255:17: error: initialization of 'void (*)(struct ptdump_state *, long unsigned int, int, u64)' {aka 'void (*)(struct ptdump_state *, long unsigned int, int, long long unsigned int)'} from incompatible pointer type 'void (*)(struct ptdump_state *, long unsigned int, int, long unsigned int)' kbuild test robot
2020-05-29 18:22 ` Andrew Morton [this message]

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=20200529112212.42e84af2ba0f1030b33658dd@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=steven.price@arm.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).