* [PATCH 1/1] async: export current_is_async()
2015-11-19 15:31 [PATCH 0/1] async: export current_is_async() Lukas Wunner
@ 2015-11-19 15:31 ` Lukas Wunner
2015-11-19 16:10 ` [PATCH 0/1] " Tejun Heo
1 sibling, 0 replies; 4+ messages in thread
From: Lukas Wunner @ 2015-11-19 15:31 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-kernel, intel-gfx
Introduced by 84b233adcca3 ("workqueue: implement current_is_async()").
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
kernel/async.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/async.c b/kernel/async.c
index 4c3773c..d2edd6e 100644
--- a/kernel/async.c
+++ b/kernel/async.c
@@ -326,3 +326,4 @@ bool current_is_async(void)
return worker && worker->current_func == async_run_entry_fn;
}
+EXPORT_SYMBOL_GPL(current_is_async);
--
2.1.0
^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH 0/1] async: export current_is_async()
@ 2015-11-19 15:31 Lukas Wunner
2015-11-19 15:31 ` [PATCH 1/1] " Lukas Wunner
2015-11-19 16:10 ` [PATCH 0/1] " Tejun Heo
0 siblings, 2 replies; 4+ messages in thread
From: Lukas Wunner @ 2015-11-19 15:31 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-kernel, intel-gfx
Hi Tejun,
when you introduced current_is_async() with 84b233adcca3, was it a
deliberate decision not to export it? All other non-static functions
in async.c are exported as well.
I'm asking because I would like to use it in i915.ko.
Thanks,
Lukas
Lukas Wunner (1):
async: export current_is_async()
kernel/async.c | 1 +
1 file changed, 1 insertion(+)
--
2.1.0
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 0/1] async: export current_is_async()
2015-11-19 15:31 [PATCH 0/1] async: export current_is_async() Lukas Wunner
2015-11-19 15:31 ` [PATCH 1/1] " Lukas Wunner
@ 2015-11-19 16:10 ` Tejun Heo
2015-11-19 16:52 ` [Intel-gfx] " Daniel Vetter
1 sibling, 1 reply; 4+ messages in thread
From: Tejun Heo @ 2015-11-19 16:10 UTC (permalink / raw)
To: Lukas Wunner; +Cc: linux-kernel, intel-gfx
Hello, Lukas.
On Thu, Nov 19, 2015 at 04:31:11PM +0100, Lukas Wunner wrote:
> Hi Tejun,
>
> when you introduced current_is_async() with 84b233adcca3, was it a
> deliberate decision not to export it? All other non-static functions
> in async.c are exported as well.
>
> I'm asking because I would like to use it in i915.ko.
There just was no module user at the time. Please feel free to export
it.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Intel-gfx] [PATCH 0/1] async: export current_is_async()
2015-11-19 16:10 ` [PATCH 0/1] " Tejun Heo
@ 2015-11-19 16:52 ` Daniel Vetter
0 siblings, 0 replies; 4+ messages in thread
From: Daniel Vetter @ 2015-11-19 16:52 UTC (permalink / raw)
To: Tejun Heo; +Cc: Lukas Wunner, intel-gfx, linux-kernel
On Thu, Nov 19, 2015 at 11:10:16AM -0500, Tejun Heo wrote:
> Hello, Lukas.
>
> On Thu, Nov 19, 2015 at 04:31:11PM +0100, Lukas Wunner wrote:
> > Hi Tejun,
> >
> > when you introduced current_is_async() with 84b233adcca3, was it a
> > deliberate decision not to export it? All other non-static functions
> > in async.c are exported as well.
> >
> > I'm asking because I would like to use it in i915.ko.
>
> There just was no module user at the time. Please feel free to export
> it.
I take that as an ack to pull Lukas' export patch in through drm-intel
trees.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-19 16:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-19 15:31 [PATCH 0/1] async: export current_is_async() Lukas Wunner
2015-11-19 15:31 ` [PATCH 1/1] " Lukas Wunner
2015-11-19 16:10 ` [PATCH 0/1] " Tejun Heo
2015-11-19 16:52 ` [Intel-gfx] " Daniel Vetter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox