All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/4] Introduce and use ETH_P_LLDP
Date: Thu, 11 Apr 2019 09:11:32 -0700	[thread overview]
Message-ID: <20190411161136.1541-1-anirudh.venkataramanan@intel.com> (raw)

This series introduces and uses a new define ETH_P_LLDP for the
Link Layer Discovery Protocol (LLDP) ethertype. Driver specific
defines for the same value (0x88CC) were removed.

Anirudh Venkataramanan (4):
  net: Add a define for LLDP ethertype
  i40e: Use LLDP ethertype define ETH_P_LLDP
  ixgbe: Use LLDP ethertype define ETH_P_LLDP
  net: hns3: Use LLDP ethertype define ETH_P_LLDP

 drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h  | 1 -
 drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 2 +-
 drivers/net/ethernet/intel/i40e/i40e.h                  | 2 --
 drivers/net/ethernet/intel/i40e/i40e_debugfs.c          | 4 ++--
 drivers/net/ethernet/intel/ixgbe/ixgbe.h                | 2 --
 drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c          | 2 +-
 include/uapi/linux/if_ether.h                           | 1 +
 7 files changed, 5 insertions(+), 9 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-04-11 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 16:11 Anirudh Venkataramanan [this message]
2019-04-11 16:11 ` [Intel-wired-lan] [PATCH 1/4] net: Add a define for LLDP ethertype Anirudh Venkataramanan
2019-04-19 17:13   ` Bowers, AndrewX
2019-04-11 16:11 ` [Intel-wired-lan] [PATCH 2/4] i40e: Use LLDP ethertype define ETH_P_LLDP Anirudh Venkataramanan
2019-04-30 23:22   ` Bowers, AndrewX
2019-04-11 16:11 ` [Intel-wired-lan] [PATCH 3/4] ixgbe: " Anirudh Venkataramanan
2019-04-19 17:13   ` Bowers, AndrewX
2019-04-11 16:11 ` [Intel-wired-lan] [PATCH 4/4] net: hns3: " Anirudh Venkataramanan
2019-04-19 17:14   ` Bowers, AndrewX

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=20190411161136.1541-1-anirudh.venkataramanan@intel.com \
    --to=anirudh.venkataramanan@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 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.