From: Patrick McHardy <kaber@trash.net>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: VLAN patch: Export symbols as non GPL symbols.
Date: Mon, 26 Jan 2009 18:05:53 +0100 [thread overview]
Message-ID: <497DED71.50900@trash.net> (raw)
In-Reply-To: <497DEC7A.1040405@candelatech.com>
Ben Greear wrote:
> 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>
I added that export after moving the code from a header file, but
there's no reason from my side not to export this to non-GPLed
drivers, using _GPL was merely a habit.
Acked-by: Patrick McHardy <kaber@trash.net>
next prev parent reply other threads:[~2009-01-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 17:01 VLAN patch: Export symbols as non GPL symbols Ben Greear
2009-01-26 17:05 ` Patrick McHardy [this message]
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=497DED71.50900@trash.net \
--to=kaber@trash.net \
--cc=greearb@candelatech.com \
--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).