From: john.hubbard@gmail.com
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
linux-mm@kvack.org, John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH] Change mm debug routines back to EXPORT_SYMBOL
Date: Thu, 13 Mar 2014 19:30:46 -0700 [thread overview]
Message-ID: <1394764246-19936-2-git-send-email-jhubbard@nvidia.com> (raw)
In-Reply-To: <1394764246-19936-1-git-send-email-jhubbard@nvidia.com>
From: John Hubbard <jhubbard@nvidia.com>
A new dump_page() routine was recently added, and marked
EXPORT_SYMBOL_GPL. This routine was also added to the
VM_BUG_ON_PAGE() macro, and so the end result is that non-GPL
code can no longer call get_page() and a few other routines.
This trivial patch simply changes dump_page() to be
EXPORT_SYMBOL.
Signed-off-by: John Hubbard <jhubbard@nvidia.com>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 3bac76a..7a92925 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -6564,4 +6564,4 @@ void dump_page(struct page *page, char *reason)
{
dump_page_badflags(page, reason, 0);
}
-EXPORT_SYMBOL_GPL(dump_page);
+EXPORT_SYMBOL(dump_page);
--
1.9.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-14 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 2:30 [PATCH] A long explanation for a short patch john.hubbard
2014-03-14 2:30 ` john.hubbard [this message]
2014-03-14 4:36 ` Sasha Levin
2014-03-14 4:47 ` John Hubbard
2014-03-14 13:42 ` Josh Boyer
2014-03-14 15:09 ` Sasha Levin
2014-03-14 16:53 ` Josh Boyer
2014-04-01 23:08 ` Andrew Morton
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=1394764246-19936-2-git-send-email-jhubbard@nvidia.com \
--to=john.hubbard@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).