From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ani Sinha <ani@arista.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
fruggeri <fruggeri@arista.com>,
Ivan Delalande <colona@arista.com>
Subject: Re: kernel_thread() for non-GPL drivers
Date: Tue, 2 Jun 2015 21:31:38 +0100 [thread overview]
Message-ID: <20150602203138.GK7232@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOxq_8PjG2Hzcdug-G7PJEcP8x02n+ezAw5AiEWpn71RjNt7ww@mail.gmail.com>
On Tue, Jun 02, 2015 at 12:43:15PM -0700, Ani Sinha wrote:
> So my question to you is, which api (for x86) are drivers supposed to
> use if kernel_thread() is no longer available? It looks to me like
> maybe we can use kthread_run() which eventually lazily creates a
> kernel thread. Is my understanding correct?
First of all, what the hell does it have to do with GPL? Or modules
vs. built-in, for that matter... kernel_thread() is _not_ what it
used to be way back and export or no export, your driver isn't going
to be happy with it.
kthread_run() had been there for more than 11 years, for crying out loud!
prev parent reply other threads:[~2015-06-02 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 19:43 kernel_thread() for non-GPL drivers Ani Sinha
2015-06-02 20:31 ` Al Viro [this message]
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=20150602203138.GK7232@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ani@arista.com \
--cc=colona@arista.com \
--cc=fruggeri@arista.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox