From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
Andrew Bowers <andrewx.bowers@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next 04/15] ice: Remove braces for single statement blocks
Date: Thu, 23 May 2019 15:33:29 -0700 [thread overview]
Message-ID: <20190523223340.13449-5-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <20190523223340.13449-1-jeffrey.t.kirsher@intel.com>
From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Fix checkpatch warning "WARNING:BRACES: braces {} are not necessary
for single statement blocks"
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c b/drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c
index 693f5d09326a..80d01ee2e967 100644
--- a/drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c
+++ b/drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c
@@ -1903,9 +1903,8 @@ static int ice_vc_cfg_qs_msg(struct ice_vf *vf, u8 *msg)
}
vsi = pf->vsi[vf->lan_vsi_idx];
- if (!vsi) {
+ if (!vsi)
goto error_param;
- }
if (qci->num_queue_pairs > ICE_MAX_BASE_QS_PER_VF) {
dev_err(&pf->pdev->dev,
--
2.21.0
next prev parent reply other threads:[~2019-05-23 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 22:33 [net-next 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2019-05-23 Jeff Kirsher
2019-05-23 22:33 ` [net-next 01/15] ice: Fix double spacing Jeff Kirsher
2019-05-23 22:33 ` [net-next 02/15] ice: Implement LLDP persistence Jeff Kirsher
2019-05-23 22:33 ` [net-next 03/15] ice: Cleanup an unnecessary variable initialization Jeff Kirsher
2019-05-23 22:33 ` Jeff Kirsher [this message]
2019-05-23 22:33 ` [net-next 05/15] ice: Call out dev/func caps when printing Jeff Kirsher
2019-05-23 22:33 ` [net-next 06/15] ice: Fix hang when ethtool disables FW LLDP Jeff Kirsher
2019-05-23 22:33 ` [net-next 07/15] ice: Advertise supported link modes if none requested Jeff Kirsher
2019-05-23 22:33 ` [net-next 08/15] ice: Refactor the LLDP MIB change event handling Jeff Kirsher
2019-05-23 22:33 ` [net-next 09/15] ice: Gracefully handle reset failure in ice_alloc_vfs() Jeff Kirsher
2019-05-23 22:33 ` [net-next 10/15] ice: Format ethtool reported stats Jeff Kirsher
2019-05-23 22:33 ` [net-next 11/15] ice: Reorganize tx_buf and ring structs Jeff Kirsher
2019-05-23 22:33 ` [net-next 12/15] ice: Use bitfields when possible Jeff Kirsher
2019-05-23 22:33 ` [net-next 13/15] ice: Reorganize ice_vf struct Jeff Kirsher
2019-05-23 22:33 ` [net-next 14/15] ice: Fix couple of issues in ice_vsi_release Jeff Kirsher
2019-05-23 22:33 ` [net-next 15/15] ice: Silence semantic parser warnings Jeff Kirsher
2019-05-24 0:54 ` [net-next 00/15][pull request] 100GbE Intel Wired LAN Driver Updates 2019-05-23 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=20190523223340.13449-5-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=andrewx.bowers@intel.com \
--cc=anirudh.venkataramanan@intel.com \
--cc=davem@davemloft.net \
--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).