All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <aduyck@mirantis.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 0/2] Two clean-ups for recent ixgbe VLAN changes
Date: Wed, 06 Jan 2016 22:48:34 -0800	[thread overview]
Message-ID: <20160107064516.12239.98349.stgit@localhost.localdomain> (raw)

These two patches clean up some minor left-overs from the recent VLAN
changes I had submitted.  With the first patch we should be able to avoid
having the PF leave any entries in the VLVF unless one of the VFs has made
use of the VLAN in which case we end up with a shared VLVF entry being
created for both the PF and the VF.  The other patch just prevents us from
looping through the setup for VLAN 0 twice.

---

Alexander Duyck (2):
      ixgbe: Do not allow PF to add VLVF entry unless it actually needs it
      ixgbe: Avoid adding VLAN 0 twice to VLVF and VFTA


 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c  |   12 +++++----
 drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c |   31 +++++++++++++-----------
 2 files changed, 23 insertions(+), 20 deletions(-)

--

             reply	other threads:[~2016-01-07  6:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  6:48 Alexander Duyck [this message]
2016-01-07  6:48 ` [Intel-wired-lan] [next PATCH 1/2] ixgbe: Do not allow PF to add VLVF entry unless it actually needs it Alexander Duyck
2016-01-15 16:20   ` Schmitt, Phillip J
2016-01-07  6:48 ` [Intel-wired-lan] [next PATCH 2/2] ixgbe: Avoid adding VLAN 0 twice to VLVF and VFTA Alexander Duyck
2016-01-15 16:20   ` Schmitt, Phillip J

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=20160107064516.12239.98349.stgit@localhost.localdomain \
    --to=aduyck@mirantis.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.