From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 1/2] riscv: Rework riscv_cpu_probe for current event macros
Date: Tue, 5 Sep 2023 17:02:58 +0800 [thread overview]
Message-ID: <ZPbuwr78alzD1yA5@swlinux02> (raw)
In-Reply-To: <9cc69902-f8d7-4b86-b071-f293463a8f5d@canonical.com>
Hi Heinrich,
On Tue, Sep 05, 2023 at 10:58:31AM +0200, Heinrich Schuchardt wrote:
> On 05.09.23 05:01, Leo Liang wrote:
> > Hi Tom,
> >
> > On Mon, Sep 04, 2023 at 03:06:34PM -0400, Tom Rini wrote:
> > > This function should now be a EVENT_SPY_SIMPLE call, update it.
> > >
> > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > ---
> > > arch/riscv/cpu/cpu.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/riscv/cpu/cpu.c b/arch/riscv/cpu/cpu.c
> > > index d64aa330f206..cfe9fdc9df55 100644
> > > --- a/arch/riscv/cpu/cpu.c
> > > +++ b/arch/riscv/cpu/cpu.c
> > > @@ -66,7 +66,7 @@ static inline bool supports_extension(char ext)
> > > #endif /* CONFIG_CPU */
> > > }
> > > -static int riscv_cpu_probe(void *ctx, struct event *event)
> > > +static int riscv_cpu_probe(void)
> > > {
> > > #ifdef CONFIG_CPU
> > > int ret;
> > > @@ -79,7 +79,7 @@ static int riscv_cpu_probe(void *ctx, struct event *event)
> > > return 0;
> > > }
> > > -EVENT_SPY(EVT_DM_POST_INIT_R, riscv_cpu_probe);
> > > +EVENT_SPY_SIMPLE(EVT_DM_POST_INIT_R, riscv_cpu_probe);
> >
> > I cannot seem to find macro "EVENT_SPY_SIMPLE".
> > Is there anything that should be added?
> > Or did I miss anything?
>
> This patch is only applicable to origin/next. The definition there is in
> include/event.h:311.
>
Thanks for the pointer!
Best regards,
Leo
> Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
>
next prev parent reply other threads:[~2023-09-05 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 19:06 [PATCH 1/2] riscv: Rework riscv_cpu_probe for current event macros Tom Rini
2023-09-04 19:06 ` [PATCH 2/2] riscv: Correct event usage for riscv_cpu_probe/setup Tom Rini
2023-09-05 17:20 ` Milan P. Stanić
2023-09-05 3:01 ` [PATCH 1/2] riscv: Rework riscv_cpu_probe for current event macros Leo Liang
2023-09-05 8:58 ` Heinrich Schuchardt
2023-09-05 9:02 ` Leo Liang [this message]
2023-09-05 17:17 ` Milan P. Stanić
2023-09-06 17:50 ` Tom Rini
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=ZPbuwr78alzD1yA5@swlinux02 \
--to=ycliang@andestech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.