All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Milone <alberto.milone@canonical.com>
To: linux-fsdevel@vger.kernel.org
Cc: mingo@kernel.org, bigeasy@linutronix.de
Subject: [PATCH 1/1] radix-tree: do not export radix_tree_preloads as GPL
Date: Fri, 17 Jul 2020 12:18:48 +0200	[thread overview]
Message-ID: <20200717101848.1869465-1-alberto.milone@canonical.com> (raw)

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().

The change breaks the NVIDIA 390 legacy driver.

This commit uses EXPORT_PER_CPU_SYMBOL() for
radix_tree_preloads.

Signed-off-by: Alberto Milone <alberto.milone@canonical.com>
---
 lib/radix-tree.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/radix-tree.c b/lib/radix-tree.c
index 34e406fe561f..5f3ec9be6e37 100644
--- a/lib/radix-tree.c
+++ b/lib/radix-tree.c
@@ -61,7 +61,7 @@ struct kmem_cache *radix_tree_node_cachep;
 DEFINE_PER_CPU(struct radix_tree_preload, radix_tree_preloads) = {
 	.lock = INIT_LOCAL_LOCK(lock),
 };
-EXPORT_PER_CPU_SYMBOL_GPL(radix_tree_preloads);
+EXPORT_PER_CPU_SYMBOL(radix_tree_preloads);
 
 static inline struct radix_tree_node *entry_to_node(void *ptr)
 {
-- 
2.25.1


             reply	other threads:[~2020-07-17 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 10:18 Alberto Milone [this message]
2020-07-17 10:43 ` [PATCH 1/1] radix-tree: do not export radix_tree_preloads as GPL Sebastian Andrzej Siewior
     [not found]   ` <ba5d59f6-2e40-d13a-ecc8-d8430a1b6a14@canonical.com>
2020-07-17 12:35     ` Fwd: " Alberto Milone
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=20200717101848.1869465-1-alberto.milone@canonical.com \
    --to=alberto.milone@canonical.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mingo@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.