From: "Leech, Christopher" <christopher.leech@intel.com>
To: "'David S. Miller'" <davem@redhat.com>,
"Leech, Christopher" <christopher.leech@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: RE: [BETA-0.92] Third test release of Tigon3 driver
Date: Thu, 28 Feb 2002 15:11:45 -0800 [thread overview]
Message-ID: <BD9B60A108C4D511AAA10002A50708F22C1451@orsmsx118.jf.intel.com> (raw)
Sounds good to me, this should work nicely.
Chris
> -----Original Message-----
> From: David S. Miller [mailto:davem@redhat.com]
> Sent: Thursday, February 28, 2002 2:57 PM
>
> This is exactly the kind of thing I wanted people to discover
> and discuss. Thanks for bringing this up.
>
> It would be quite simple to hook back into your driver for this
> purpose, proposed API:
>
> /* For netdev->features */
> #define NETIF_F_HW_VLAN_FILTER 1024
>
> /* For NETIF_F_VLAN_RX_FILTER devices */
> void (*vlan_rx_new_vid)(struct net_device *dev,
> unsigned short vid);
>
> We call dev->vlan_rx_kill_vid() in all cases because it has to
> deal with interlocking, as described in an earlier email.
>
> But if NETIF_F_HW_VLAN_FILTER is set, when new VLAN devices are
> registered that go through your card, you will get a
> dev->vlan_rx_new_vid() call.
>
> I do not think you would need any more informatin than the
> VID itself. If this is wrong, tell me now :-)
>
next reply other threads:[~2002-02-28 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 23:11 Leech, Christopher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 21:57 Leech, Christopher
2002-02-28 22:57 ` David S. Miller
2002-02-27 13:51 David S. Miller
2002-02-27 15:44 ` Jeff Garzik
2002-02-28 17:22 ` Pasi Kärkkäinen
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=BD9B60A108C4D511AAA10002A50708F22C1451@orsmsx118.jf.intel.com \
--to=christopher.leech@intel.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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
all inboxes | Powered by JetHome®