From: Ben Greear <greearb@candelatech.com>
To: Patrick McHardy <kaber@trash.net>, NetDev <netdev@vger.kernel.org>
Subject: VLAN patch: Export symbols as non GPL symbols.
Date: Mon, 26 Jan 2009 09:01:46 -0800 [thread overview]
Message-ID: <497DEC7A.1040405@candelatech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
In previous kernels, any kernel module could get access to the
'real-device' and the
VLAN-ID for a particular VLAN. In more recent kernels, the code was
restructured
such that this is hard to do without accessing private .h files for any
module that cannot
use GPL-only symbols.
Attached is a patch to once again allow non-GPL modules the ability to
access the
real-device and VLAN id for VLANs. This patch is against 2.6.29-rc2.
Signed-Off-By: Ben Greear<greearb@candelatech.com>
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
[-- Attachment #2: vlan_export.patch --]
[-- Type: text/x-patch, Size: 652 bytes --]
diff --git a/net/8021q/vlan_core.c b/net/8021q/vlan_core.c
index 6c13239..e9db889 100644
--- a/net/8021q/vlan_core.c
+++ b/net/8021q/vlan_core.c
@@ -62,13 +62,13 @@ struct net_device *vlan_dev_real_dev(const struct net_device *dev)
{
return vlan_dev_info(dev)->real_dev;
}
-EXPORT_SYMBOL_GPL(vlan_dev_real_dev);
+EXPORT_SYMBOL(vlan_dev_real_dev);
u16 vlan_dev_vlan_id(const struct net_device *dev)
{
return vlan_dev_info(dev)->vlan_id;
}
-EXPORT_SYMBOL_GPL(vlan_dev_vlan_id);
+EXPORT_SYMBOL(vlan_dev_vlan_id);
static int vlan_gro_common(struct napi_struct *napi, struct vlan_group *grp,
unsigned int vlan_tci, struct sk_buff *skb)
next reply other threads:[~2009-01-26 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 17:01 Ben Greear [this message]
2009-01-26 17:05 ` VLAN patch: Export symbols as non GPL symbols Patrick McHardy
2009-01-26 20:37 ` David Miller
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=497DEC7A.1040405@candelatech.com \
--to=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).