From: Hans-Peter Jansen <hpj@urpla.net>
To: Tejun Heo <tj@kernel.org>
Cc: tim.gardner@canonical.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules
Date: Thu, 03 Sep 2015 11:20:54 +0200 [thread overview]
Message-ID: <5012460.vcYIRW5pg5@xrated> (raw)
In-Reply-To: <20150804180520.GE17598@mtj.duckdns.org>
On Dienstag, 4. August 2015 14:05:20 Tejun Heo wrote:
> On Tue, Aug 04, 2015 at 11:26:04AM -0600, tim.gardner@canonical.com wrote:
> > From: Tim Gardner <tim.gardner@canonical.com>
> >
> > Commit 37b1ef31a568fc02e53587620226e5f3c66454c8 ("workqueue: move
> > flush_scheduled_work() to workqueue.h") moved the exported non GPL
> > flush_scheduled_work() from a function to an inline wrapper.
> > Unfortunately, it directly calls flush_workqueue() which is a GPL
> > function.
> > This has the effect of changing the licensing requirement for this
> > function
> > and makes it unavailable to non GPL modules.
> >
> > See commit ad7b1f841f8a54c6d61ff181451f55b68175e15a ("workqueue: Make
> > schedule_work() available again to non GPL modules") for precedent.
> >
> > Cc: Tejun Heo <tj@kernel.org>
> > Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
>
> Applied to wq/for-4.3.
>
> Thanks.
Tejun, mind CCing stable in this regard?
As things stand right now, it's activily deferring 4.2 rollout for (evil,
sure) nvidia users like me.
Thanks,
Pete
next prev parent reply other threads:[~2015-09-03 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 17:26 [PATCH 4.2-rc5] workqueue: Make flush_workqueue() available again to non GPL modules tim.gardner
2015-08-04 18:05 ` Tejun Heo
2015-09-03 9:20 ` Hans-Peter Jansen [this message]
2015-09-03 16:14 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 9:52 David Laight
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=5012460.vcYIRW5pg5@xrated \
--to=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox