From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: olteanv@gmail.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: Prevent usage of NET_DSA_TAG_8021Q as tagging protocol
Date: Mon, 11 Nov 2019 11:55:54 -0800 [thread overview]
Message-ID: <1f653232-c877-069d-8412-ef141dcf0dab@gmail.com> (raw)
In-Reply-To: <20191111195421.11619-1-f.fainelli@gmail.com>
On 11/11/19 11:54 AM, Florian Fainelli wrote:
> It is possible for a switch driver to use NET_DSA_TAG_8021Q as a valid
> DSA tagging protocol since it registers itself as such, unfortunately
> since there are not xmit or rcv functions provided, the lack of a xmit()
> function will lead to a NPD in dsa_slave_xmit() to start with.
>
> net/dsa/tag_8021q.c is only comprised of a set of helper functions at
> the moment, but is not a fully autonomous or functional tagging "driver"
> (though it could become later on). We do not have any users of
> NET_DSA_TAG_8021Q so now is a good time to make sure there are not
> issues being encountered by making this file strictly a place holder for
> helper functions.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
[snip]
> -static const struct dsa_device_ops dsa_8021q_netdev_ops = {
> - .name = "8021q",
> - .proto = DSA_TAG_PROTO_8021Q,
> - .overhead = VLAN_HLEN,
> -};
> -
> -MODULE_LICENSE("GPL v2");
I probably need to keep that around to avoid complaints about the module
tainting the kernel, expect a v2 based on that and/or reviewer comments.
--
Florian
next prev parent reply other threads:[~2019-11-11 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:54 [PATCH net-next] net: dsa: Prevent usage of NET_DSA_TAG_8021Q as tagging protocol Florian Fainelli
2019-11-11 19:55 ` Florian Fainelli [this message]
2019-11-11 21:29 ` Vladimir Oltean
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=1f653232-c877-069d-8412-ef141dcf0dab@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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).