[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230118110215.yexhgghqmmmkibsi@houat>
Date: Wed, 18 Jan 2023 12:02:15 +0100
From: Maxime Ripard <maxime@...no.tech>
To: David Gow <davidgow@...gle.com>
Cc: Arnd Bergmann <arnd@...nel.org>,
Brendan Higgins <brendan.higgins@...ux.dev>,
Arnd Bergmann <arnd@...db.de>,
Shuah Khan <skhan@...uxfoundation.org>,
Daniel Latypov <dlatypov@...gle.com>,
Jeremy Kerr <jk@...econstruct.com.au>,
Joe Fradley <joefradley@...gle.com>,
Javier Martinez Canillas <javierm@...hat.com>,
MaĆra Canal <mcanal@...lia.com>,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kunit: Export kunit_running()
Hi David, Arnd,
Thanks for fixing this issue
On Wed, Jan 18, 2023 at 08:37:26AM +0800, David Gow wrote:
> On Wed, 18 Jan 2023 at 00:50, Arnd Bergmann <arnd@...nel.org> wrote:
> >
> > From: Arnd Bergmann <arnd@...db.de>
> >
> > Using kunit_fail_current_test() in a loadable module causes a link
> > error like:
> >
> > ERROR: modpost: "kunit_running" [drivers/gpu/drm/vc4/vc4.ko] undefined!
> >
> > Export the symbol to allow using it from modules.
> >
> > Fixes: da43ff045c3f ("drm/vc4: tests: Fail the current test if we access a register")
> > Signed-off-by: Arnd Bergmann <arnd@...db.de>
> > ---
>
> Thanks for fixing this!
>
> I think the longer-term solution for this is the "hooks" approach
> (which works even when KUnit itself is built as a module):
> https://lore.kernel.org/all/20230117142737.246446-1-davidgow@google.com/
>
> But this looks good to fix it in the meantime.
>
> Reviewed-by: David Gow <davidgow@...gle.com>
How do you want to merge that patch? Will you take it through your tree?
Maxime
Powered by blists - more mailing lists