public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: linux-riscv@lists.infradead.org
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	christoph.muellner@vrull.eu, philipp.tomsich@vrull.eu,
	abrestic@rivosinc.com, Conor Dooley <conor@kernel.org>
Subject: Re: [PATCH] RISC-V: Fix do_notify_resume / do_work_pending prototype
Date: Fri, 27 Jan 2023 14:59:59 +0100	[thread overview]
Message-ID: <3463308.V25eIC5XRa@diego> (raw)
In-Reply-To: <Y8gTBJsB22LSzZFy@spud>

Am Mittwoch, 18. Januar 2023, 16:40:52 CET schrieb Conor Dooley:
> On Wed, Jan 18, 2023 at 03:22:52PM +0100, Heiko Stuebner wrote:
> > From: Heiko Stuebner <heiko.stuebner@vrull.eu>
> > 
> > Commit b0f4c74eadbf ("RISC-V: Fix unannoted hardirqs-on in return to
> > userspace slow-path") renamed the do_notify_resume function to
> > do_work_pending but did not change the prototype in signal.h
> > Do that now, as the original function does not exist anymore.
> > 
> > Fixes: b0f4c74eadbf ("RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path")
> > Signed-off-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
> > ---
> >  arch/riscv/include/asm/signal.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/riscv/include/asm/signal.h b/arch/riscv/include/asm/signal.h
> > index 532c29ef0376..956ae0a01bad 100644
> > --- a/arch/riscv/include/asm/signal.h
> > +++ b/arch/riscv/include/asm/signal.h
> > @@ -7,6 +7,6 @@
> >  #include <uapi/asm/ptrace.h>
> >  
> >  asmlinkage __visible
> > -void do_notify_resume(struct pt_regs *regs, unsigned long thread_info_flags);
> > +void do_work_pending(struct pt_regs *regs, unsigned long thread_info_flags);
> 
> Is that an auto-builder blind spot as it gets jumped to from asm?

Yeah, the prototype is seemingly more for show in that case, as I guess
from asm we only look for the symbol itself but nothing will check the
syntax of the parameters.


@Palmer: any thoughts?


Thanks
Heiko



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-01-27 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 14:22 [PATCH] RISC-V: Fix do_notify_resume / do_work_pending prototype Heiko Stuebner
2023-01-18 15:10 ` Andrew Jones
2023-01-18 15:40 ` Conor Dooley
2023-01-27 13:59   ` Heiko Stübner [this message]
2023-01-31 18:30 ` patchwork-bot+linux-riscv

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=3463308.V25eIC5XRa@diego \
    --to=heiko@sntech.de \
    --cc=abrestic@rivosinc.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=conor@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    /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