From: David Miller <davem@davemloft.net>
To: vyasevic@redhat.com
Cc: netdev@vger.kernel.org, john.r.fastabend@intel.com
Subject: Re: [PATCH v2 net-next 0/4] Provide default fdb operation to allow mac filter setting
Date: Fri, 01 Mar 2013 16:26:12 -0500 (EST) [thread overview]
Message-ID: <20130301.162612.2115492006742815404.davem@davemloft.net> (raw)
In-Reply-To: <1362151906-20993-1-git-send-email-vyasevic@redhat.com>
From: Vlad Yasevich <vyasevic@redhat.com>
Date: Fri, 1 Mar 2013 10:31:42 -0500
> This is a short series that now allows mac filter programming on any
> card that support IFF_UNICAST_FLT by using the existing FDB interface.
>
> Some existing drivers that had FDB functionality usually supported
> it only in SR-IOV mode. Since that's not always enabled, and
> we want to take advantage of IFF_UNICAST_FLT support, these drivers
> have been converted to call the default handler when not in SRIOV mode.
These changes look great, please resubmit them once I open net-next
back up.
Thanks.
next prev parent reply other threads:[~2013-03-01 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 15:31 [PATCH v2 net-next 0/4] Provide default fdb operation to allow mac filter setting Vlad Yasevich
2013-03-01 15:31 ` [PATCH v2 net-next 1/4] net: generic fdb support for drivers without ndo_fdb_<op> Vlad Yasevich
2013-03-01 22:20 ` John Fastabend
2013-03-01 15:31 ` [PATCH v2 net-next 2/4] ixgbe: Remove driver specific fdb handlers Vlad Yasevich
2013-03-01 22:22 ` John Fastabend
2013-03-01 15:31 ` [PATCH v2 net-next 3/4] mlx4: " Vlad Yasevich
2013-03-01 15:31 ` [PATCH v2 net-next 4/4] qlcnic: Use generic fdb handler when driver options are not enabled Vlad Yasevich
2013-03-01 21:26 ` David Miller [this message]
2013-03-06 20:37 ` [PATCH v2 net-next 0/4] Provide default fdb operation to allow mac filter setting Or Gerlitz
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=20130301.162612.2115492006742815404.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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).