All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rose, Gregory V" <gregory.v.rose@intel.com>
To: David Miller <davem@davemloft.net>, "joe@perches.com" <joe@perches.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"gospo@redhat.com" <gospo@redhat.com>,
	"sassmann@redhat.com" <sassmann@redhat.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [net 2/8] igb: fix vf lookup
Date: Wed, 8 Feb 2012 23:55:10 +0000	[thread overview]
Message-ID: <C5551D9AAB213A418B7FD5E4A6F30A0702F862AE@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <20120208.185244.1488314318862923939.davem@davemloft.net>

> -----Original Message-----
> From: David Miller [mailto:davem@davemloft.net]
> Sent: Wednesday, February 08, 2012 3:53 PM
> To: joe@perches.com
> Cc: Rose, Gregory V; Kirsher, Jeffrey T; netdev@vger.kernel.org;
> gospo@redhat.com; sassmann@redhat.com; stable@vger.kernel.org
> Subject: Re: [net 2/8] igb: fix vf lookup
> 
> From: Joe Perches <joe@perches.com>
> Date: Wed, 08 Feb 2012 15:49:40 -0800
> 
> > On Wed, 2012-02-08 at 23:42 +0000, Rose, Gregory V wrote:
> >> > diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
> > []
> >> > @@ -5012,7 +5012,8 @@ static int igb_find_enabled_vfs(struct
> igb_adapter
> >> > *adapter)
> >> >  	vf_devfn = pdev->devfn + 0x80;
> >> >  	pvfdev = pci_get_device(hw->vendor_id, device_id, NULL);
> >> >  	while (pvfdev) {
> >> > -		if (pvfdev->devfn == vf_devfn)
> >> > +		if (pvfdev->devfn == vf_devfn &&
> >> > +		    (pvfdev->bus->number >= pdev->bus->number))
> >> >  			vfs_found++;
> > []
> >> I'll fix this one too.  You start leaning on checkpatch and you get
> lazy I guess.
> >
> > I suppose an indentation rule could be created when
> > arguments on multiple lines don't align at the open
> > parenthesis, but I'm not going to rewrite emacs
> > indentation rules.
> >
> > Presumably it should only be used with --strict.
> >
> > Anyone think multiple line tests with inequivalent uses
> > of parentheses like this one should be noted as well?
> 
> Actually I thought this case was perfectly fine.

The imbalanced parenthesis usage bothers me.  And yes, if you're going to have a tool that checks patch formatting it'd be nice if it caught things like this.  But then I'm the lazy fool here...

- Greg

  reply	other threads:[~2012-02-08 23:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  9:36 [net 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-02-08  9:36 ` [net 1/8] e1000: add dropped DMA receive enable back in for WoL Jeff Kirsher
2012-02-08  9:36 ` [net 2/8] igb: fix vf lookup Jeff Kirsher
2012-02-08 23:42   ` Rose, Gregory V
2012-02-08 23:49     ` Joe Perches
2012-02-08 23:52       ` David Miller
2012-02-08 23:55         ` Rose, Gregory V [this message]
2012-02-09  9:10       ` Jeff Kirsher
2012-02-08  9:36 ` [net 3/8] ixgbe: " Jeff Kirsher
2012-02-08 23:33   ` David Miller
2012-02-08 23:39     ` Rose, Gregory V
2012-02-09  9:06     ` Jeff Kirsher
2012-02-08  9:36 ` [net 4/8] ixgbe: Fix case of Tx Hang in PF with 32 VFs Jeff Kirsher
2012-02-08  9:36 ` [net 5/8] ixgbe: Fix broken dependency on MAX_SKB_FRAGS being related to page size Jeff Kirsher
2012-02-08  9:36 ` [net 6/8] ixgbe: do not update real num queues when netdev is going away Jeff Kirsher
2012-02-08  9:36 ` [net 7/8] ixgbe: dcb: up2tc mapping lost on disable/enable CEE DCB state Jeff Kirsher
2012-02-08  9:36 ` [net 8/8] ixgbe: ethtool: stats user buffer overrun Jeff Kirsher
2012-02-08 15:17   ` Ben Hutchings
2012-02-09  9:34 [net v2 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-02-09  9:34 ` [net 2/8] igb: fix vf lookup Jeff Kirsher

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=C5551D9AAB213A418B7FD5E4A6F30A0702F862AE@ORSMSX106.amr.corp.intel.com \
    --to=gregory.v.rose@intel.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=joe@perches.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    --cc=stable@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 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.