From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 4/4] net: hns3: Use LLDP ethertype define ETH_P_LLDP
Date: Fri, 19 Apr 2019 17:14:24 +0000 [thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A1D38EE38@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <20190411161136.1541-5-anirudh.venkataramanan@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Anirudh Venkataramanan
> Sent: Thursday, April 11, 2019 9:12 AM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH 4/4] net: hns3: Use LLDP ethertype define
> ETH_P_LLDP
>
> Remove references to HCLGE_MAC_ETHERTYPE_LLDP and use ETH_P_LLDP
> instead.
>
> Signed-off-by: Anirudh Venkataramanan
> <anirudh.venkataramanan@intel.com>
> ---
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 1 -
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
prev parent reply other threads:[~2019-04-19 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 16:11 [Intel-wired-lan] [PATCH 0/4] Introduce and use ETH_P_LLDP Anirudh Venkataramanan
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 [this message]
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=26D9FDECA4FBDD4AADA65D8E2FC68A4A1D38EE38@ORSMSX104.amr.corp.intel.com \
--to=andrewx.bowers@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.