netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Mark Rustad <mark.d.rustad@intel.com>,
	netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next 04/12] ixgbe: Fix ixgbe_write_mbx error result
Date: Fri, 25 Jul 2014 21:45:14 -0700	[thread overview]
Message-ID: <1406349922-9883-5-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1406349922-9883-1-git-send-email-jeffrey.t.kirsher@intel.com>

From: Mark Rustad <mark.d.rustad@intel.com>

If ixgbe_write_mbx is called and no mbx->ops.write method
exists, no error code is returned. The corresponding read
function explicitly returns an error in such a case as do
other functions, so this appears to be a minor bug. Fix
it for consistency, and generate return values directly
to make things clearer.

Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
 drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.c | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.c
index 1918e0a..5047957 100644
--- a/drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.c
+++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.c
@@ -1,7 +1,7 @@
 /*******************************************************************************
 
   Intel 10 Gigabit PCI Express Linux driver
-  Copyright(c) 1999 - 2013 Intel Corporation.
+  Copyright(c) 1999 - 2014 Intel Corporation.
 
   This program is free software; you can redistribute it and/or modify it
   under the terms and conditions of the GNU General Public License,
@@ -67,15 +67,14 @@ s32 ixgbe_read_mbx(struct ixgbe_hw *hw, u32 *msg, u16 size, u16 mbx_id)
 s32 ixgbe_write_mbx(struct ixgbe_hw *hw, u32 *msg, u16 size, u16 mbx_id)
 {
 	struct ixgbe_mbx_info *mbx = &hw->mbx;
-	s32 ret_val = 0;
 
 	if (size > mbx->size)
-		ret_val = IXGBE_ERR_MBX;
+		return IXGBE_ERR_MBX;
 
-	else if (mbx->ops.write)
-		ret_val = mbx->ops.write(hw, msg, size, mbx_id);
+	if (!mbx->ops.write)
+		return IXGBE_ERR_MBX;
 
-	return ret_val;
+	return mbx->ops.write(hw, msg, size, mbx_id);
 }
 
 /**
-- 
1.9.3

  parent reply	other threads:[~2014-07-26  4:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  4:45 [net-next 00/12][pull request] Intel Wired LAN Driver Updates 2014-07-25 Jeff Kirsher
2014-07-26  4:45 ` [net-next 01/12] ixgbe: Convert some udelays to usleep_range Jeff Kirsher
2014-07-26  4:45 ` [net-next 02/12] ixgbe: Fix spurious release of semaphore in EEPROM access Jeff Kirsher
2014-07-26  4:45 ` [net-next 03/12] ixgbe: Correct X540 semaphore error Jeff Kirsher
2014-07-26  4:45 ` Jeff Kirsher [this message]
2014-07-26  4:45 ` [net-next 05/12] ixgbe: Delete a bunch of dead code Jeff Kirsher
2014-07-26  4:45 ` [net-next 06/12] ixgbevf: Remove unused get_supported_physical_layer pointer Jeff Kirsher
2014-07-26  4:45 ` [net-next 07/12] ixgbe: Make return values more direct Jeff Kirsher
2014-07-26  4:45 ` [net-next 08/12] e1000e: Fix CRC errors with jumbo traffic Jeff Kirsher
2014-07-26  4:45 ` [net-next 09/12] e1000e: Add code to check return values on NVM accesses Jeff Kirsher
2014-07-26  4:45 ` [net-next 10/12] e1000e: Add support for EEE in Sx states Jeff Kirsher
2014-07-26  4:45 ` [net-next 11/12] e1000e: Fix EEE in S5 w/ Runtime PM enabled Jeff Kirsher
2014-07-26 15:10   ` Francois Romieu
2014-07-29 16:14     ` Ertman, David M
2014-07-29 22:11       ` Francois Romieu
2014-07-26  4:45 ` [net-next 12/12] e1000e: Fix Runtime PM blocks EEE link negotiation in S5 Jeff Kirsher
2014-07-28 19:21 ` [net-next 00/12][pull request] Intel Wired LAN Driver Updates 2014-07-25 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=1406349922-9883-5-git-send-email-jeffrey.t.kirsher@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=mark.d.rustad@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=sassmann@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).