public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	linux-riscv <linux-riscv@lists•infradead.org>,
	Alexandre Ghiti <alexghiti@rivosinc•com>
Subject: Re: linux-next: Tree for Dec 11 (drivers/perf/riscv_pmu_sbi.c)
Date: Mon, 11 Dec 2023 13:22:23 -0800	[thread overview]
Message-ID: <846f4d8a-16ad-4ce2-9bcc-34e03f057421@infradead.org> (raw)
In-Reply-To: <20231211172504.058ad6b6@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]



On 12/10/23 22:25, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20231208:
> 

on riscv32:

../drivers/perf/riscv_pmu_sbi.c:1015:35: error: initialization of 'int (*)(const struct ctl_table *, int,  void *, size_t *, loff_t *)' {aka 'int (*)(const struct ctl_table *, int,  void *, unsigned int *, long long int *)'} from incompatible pointer type 'int (*)(struct ctl_table *, int,  void *, size_t *, loff_t *)' {aka 'int (*)(struct ctl_table *, int,  void *, unsigned int *, long long int *)'} [-Werror=incompatible-pointer-types]
 1015 |                 .proc_handler   = riscv_pmu_proc_user_access_handler,
      |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/perf/riscv_pmu_sbi.c:1015:35: note: (near initialization for 'sbi_pmu_sysctl_table[0].proc_handler')



Full randconfig file is attached.


-- 
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html

[-- Attachment #2: config-r3583.gz --]
[-- Type: application/gzip, Size: 39318 bytes --]

  parent reply	other threads:[~2023-12-11 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  6:25 linux-next: Tree for Dec 11 Stephen Rothwell
2023-12-11 21:17 ` linux-next: Tree for Dec 11 (riscv32: patch.c) Randy Dunlap
2023-12-12  8:01   ` Alexandre Ghiti
2023-12-13 12:57     ` Conor Dooley
2023-12-13 13:33       ` Alexandre Ghiti
2023-12-14 10:05         ` Alexandre Ghiti
2023-12-11 21:22 ` Randy Dunlap [this message]
2023-12-12  7:24   ` linux-next: Tree for Dec 11 (drivers/perf/riscv_pmu_sbi.c) Alexandre Ghiti
2023-12-12 21:37     ` Stephen Rothwell

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=846f4d8a-16ad-4ce2-9bcc-34e03f057421@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=alexghiti@rivosinc$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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