From: Andre Guedes <andre.guedes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/4] igc: Fixes for VLAN priority filtering code
Date: Fri, 3 Apr 2020 11:17:39 -0700 [thread overview]
Message-ID: <20200403181743.23447-1-andre.guedes@intel.com> (raw)
Hi,
This patch series provides some fixes and improvements to the VLAN
priority filtering code from IGC driver.
The improvements focuses on aligning the code organization to follow
the same rationale from MAC address filtering code, splitting ethtool
and core logic between igc_ethtool.c and igc_main.c. It also adds some
log messages to help debugging the code.
Best regards,
Andre
Andre Guedes (4):
igc: Rename IGC_VLAPQF macro
igc: Dump VLANPQF register
igc: Return -EOPNOTSUPP when VLAN mask doesn't match
igc: Refactor VLAN priority filtering code
drivers/net/ethernet/intel/igc/igc.h | 3 +
drivers/net/ethernet/intel/igc/igc_defines.h | 6 +-
drivers/net/ethernet/intel/igc/igc_ethtool.c | 70 +++++---------------
drivers/net/ethernet/intel/igc/igc_main.c | 52 +++++++++++++++
drivers/net/ethernet/intel/igc/igc_regs.h | 2 +-
5 files changed, 76 insertions(+), 57 deletions(-)
--
2.26.0
next reply other threads:[~2020-04-03 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 18:17 Andre Guedes [this message]
2020-04-03 18:17 ` [Intel-wired-lan] [PATCH 1/4] igc: Rename IGC_VLAPQF macro Andre Guedes
2020-04-21 18:29 ` Brown, Aaron F
2020-04-03 18:17 ` [Intel-wired-lan] [PATCH 2/4] igc: Dump VLANPQF register Andre Guedes
2020-04-21 23:40 ` Brown, Aaron F
2020-04-03 18:17 ` [Intel-wired-lan] [PATCH 3/4] igc: Return -EOPNOTSUPP when VLAN mask doesn't match Andre Guedes
2020-04-21 23:44 ` Brown, Aaron F
2020-04-03 18:17 ` [Intel-wired-lan] [PATCH 4/4] igc: Refactor VLAN priority filtering code Andre Guedes
2020-04-04 1:55 ` Vinicius Costa Gomes
2020-04-04 3:00 ` Andre Guedes
2020-04-21 23:48 ` Brown, Aaron F
2020-04-24 1:11 ` [Intel-wired-lan] [PATCH v2 " Andre Guedes
2020-05-01 21:47 ` Brown, Aaron F
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=20200403181743.23447-1-andre.guedes@intel.com \
--to=andre.guedes@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox