From: Joe Perches <joe@perches.com>
To: netdev@vger.kernel.org
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Greg Rose <gregory.v.rose@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Mitch Williams <mitch.a.williams@intel.com>,
e1000-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 4/9] igbvf: Convert uses of __constant_<foo> to <foo>
Date: Wed, 12 Mar 2014 10:22:33 -0700 [thread overview]
Message-ID: <52ad53c6822c19de67480e8b3e36201a30cab308.1394644825.git.joe@perches.com> (raw)
In-Reply-To: <cover.1394644825.git.joe@perches.com>
The use of __constant_<foo> has been unnecessary for quite awhile now.
Make these uses consistent with the rest of the kernel.
Signed-off-by: Joe Perches <joe@perches.com>
---
drivers/net/ethernet/intel/igbvf/netdev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/intel/igbvf/netdev.c b/drivers/net/ethernet/intel/igbvf/netdev.c
index e2c6d80..b7ab03a 100644
--- a/drivers/net/ethernet/intel/igbvf/netdev.c
+++ b/drivers/net/ethernet/intel/igbvf/netdev.c
@@ -2014,12 +2014,12 @@ static inline bool igbvf_tx_csum(struct igbvf_adapter *adapter,
if (skb->ip_summed == CHECKSUM_PARTIAL) {
switch (skb->protocol) {
- case __constant_htons(ETH_P_IP):
+ case htons(ETH_P_IP):
tu_cmd |= E1000_ADVTXD_TUCMD_IPV4;
if (ip_hdr(skb)->protocol == IPPROTO_TCP)
tu_cmd |= E1000_ADVTXD_TUCMD_L4T_TCP;
break;
- case __constant_htons(ETH_P_IPV6):
+ case htons(ETH_P_IPV6):
if (ipv6_hdr(skb)->nexthdr == IPPROTO_TCP)
tu_cmd |= E1000_ADVTXD_TUCMD_L4T_TCP;
break;
--
1.8.1.2.459.gbcd45b4.dirty
next prev parent reply other threads:[~2014-03-12 17:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 17:22 [PATCH net-next 0/9] drivers/net: " Joe Perches
2014-03-12 17:22 ` [PATCH net-next 1/9] brocade: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 2/9] e100: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 3/9] igb: " Joe Perches
2014-03-12 19:30 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` Joe Perches [this message]
2014-03-12 19:29 ` [PATCH net-next 4/9] igbvf: " David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 5/9] ixgbe: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 20:50 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 6/9] ixgbevf: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 20:51 ` Jeff Kirsher
2014-03-12 17:22 ` [PATCH net-next 7/9] xilinx: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 8/9] lg-vl600: " Joe Perches
2014-03-12 19:29 ` David Miller
2014-03-12 17:22 ` [PATCH net-next 9/9] ath9k: " Joe Perches
2014-03-12 19:29 ` David Miller
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=52ad53c6822c19de67480e8b3e36201a30cab308.1394644825.git.joe@perches.com \
--to=joe@perches.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®