From: Alberto Milone <alberto.milone@canonical.com>
To: linux-fsdevel@vger.kernel.org
Subject: Fwd: [PATCH 1/1] radix-tree: do not export radix_tree_preloads as GPL
Date: Fri, 17 Jul 2020 14:35:08 +0200 [thread overview]
Message-ID: <ecfc9797-5941-7ff9-629f-8f381e844b9a@canonical.com> (raw)
In-Reply-To: <ba5d59f6-2e40-d13a-ecc8-d8430a1b6a14@canonical.com>
-------- Forwarded Message --------
Subject: Re: [PATCH 1/1] radix-tree: do not export radix_tree_preloads
as GPL
Date: Fri, 17 Jul 2020 14:33:31 +0200
From: Alberto Milone <alberto.milone@canonical.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
CC: linux-fsdevel@vger.kernel.org, mingo@kernel.org
On 17/07/2020 12:43, Sebastian Andrzej Siewior wrote:
> On 2020-07-17 12:18:48 [+0200], Alberto Milone wrote:
>> Commit cfa6705d89b6 ("radix-tree: Use local_lock
>> for protection") replaced a DEFINE_PER_CPU() with an
>> EXPORT_PER_CPU_SYMBOL_GPL(), which made the
>> radix_tree_preloads symbol GPL only. All the other
>> symbols in the file are exported with EXPORT_SYMBOL().
> Is this a problem if you disable CONFIG_DEBUG_LOCK_ALLOC ?
I checked and CONFIG_DEBUG_LOCK_ALLOC is not enabled in our kernels.
next prev parent reply other threads:[~2020-07-17 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 10:18 [PATCH 1/1] radix-tree: do not export radix_tree_preloads as GPL Alberto Milone
2020-07-17 10:43 ` Sebastian Andrzej Siewior
[not found] ` <ba5d59f6-2e40-d13a-ecc8-d8430a1b6a14@canonical.com>
2020-07-17 12:35 ` Alberto Milone [this message]
2020-07-17 13:21 ` Sebastian Andrzej Siewior
2020-07-17 13:45 ` Alberto Milone
2020-07-17 14:28 ` Seth Forshee
2020-07-17 14:31 ` Sebastian Andrzej Siewior
2020-07-17 14:34 ` Seth Forshee
[not found] ` <20200717155519.GM3644@ubuntu-x1>
2020-07-20 14:49 ` Seth Forshee
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=ecfc9797-5941-7ff9-629f-8f381e844b9a@canonical.com \
--to=alberto.milone@canonical.com \
--cc=linux-fsdevel@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 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.