From: Ingo Molnar <mingo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com
Subject: Re: [tip:WIP.sched/core 19/22] kernel/sched/core.c:2836:18: error: passing argument 1 of 'mips_install_watch_registers' from incompatible pointer type
Date: Mon, 5 Mar 2018 08:12:54 +0100 [thread overview]
Message-ID: <20180305071253.xgmpj6a5orleb6pa@gmail.com> (raw)
In-Reply-To: <b8be96d0-8a53-104e-c90d-72a3ea158f8d@infradead.org>
* Randy Dunlap <rdunlap@infradead.org> wrote:
> > kernel//sched/core.c:2836:2: note: in expansion of macro 'switch_to'
> > switch_to(prev, next, prev);
> > ^~~~~~~~~
> > arch/mips/include/asm/watch.h:15:6: note: expected 'struct task_struct *' but argument is of type 'struct task_struct *'
> > void mips_install_watch_registers(struct task_struct *t);
> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: some warnings being treated as errors
>
> I don't have a tip git repo, but it looks like this would fix it (based on most
> recent -next):
>
> --- linux-next-20180302.orig/arch/mips/include/asm/watch.h
> +++ linux-next-20180302/arch/mips/include/asm/watch.h
> @@ -12,6 +12,8 @@
>
> #include <asm/mipsregs.h>
>
> +struct task_struct;
> +
> void mips_install_watch_registers(struct task_struct *t);
> void mips_read_watch_registers(void);
> void mips_clear_watch_registers(void);
Yeah, so MIPS wasn't the only arch affected - so I fixed it by restoring the
original header order.
Thanks,
Ingo
prev parent reply other threads:[~2018-03-05 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 10:52 kbuild test robot
2018-03-04 18:12 ` Randy Dunlap
2018-03-05 7:12 ` Ingo Molnar [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=20180305071253.xgmpj6a5orleb6pa@gmail.com \
--to=mingo@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®