All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Tejun Heo <tj@kernel.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] async: export current_is_async()
Date: Thu, 19 Nov 2015 16:31:11 +0100	[thread overview]
Message-ID: <cover.1447937831.git.lukas@wunner.de> (raw)

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Lukas Wunner <lukas@wunner.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/1] async: export current_is_async()
Date: Thu, 19 Nov 2015 16:31:11 +0100	[thread overview]
Message-ID: <cover.1447937831.git.lukas@wunner.de> (raw)

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


             reply	other threads:[~2015-11-19 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 15:31 Lukas Wunner [this message]
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 15:31   ` Lukas Wunner
2015-11-19 16:10 ` [PATCH 0/1] " Tejun Heo
2015-11-19 16:10   ` Tejun Heo
2015-11-19 16:52   ` Daniel Vetter
2015-11-19 16:52     ` [Intel-gfx] " Daniel Vetter

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=cover.1447937831.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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.