From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 0/9][pull request] Intel Wired LAN Driver Updates 2014-10-23
Date: Fri, 24 Oct 2014 16:43:27 -0400 (EDT) [thread overview]
Message-ID: <20141024.164327.535125094046571848.davem@davemloft.net> (raw)
In-Reply-To: <1414123806-20049-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Thu, 23 Oct 2014 21:09:57 -0700
> This series contains updates to i40e and i40evf.
>
> Jesse modifies the i40e driver to only notify the firmware on link up/down
> and qualified module events. Also simplified the job of managing link
> state by using the admin queue receive event for link events as a signal
> to tell the driver to update link state.
>
> Jeff (me) cleans up the inconsistent use of tabs for indentation in the admin
> queue command header file.
>
> Neerav converts the use of udelay() to usleep_range().
>
> Anjali fixes a bug where receive would stop after some stress by adding
> a sleep and restart as well as moving the setting of flow control because
> it should be done at a PF level and not a VSI level.
>
> Mitch adds code to handle link events when updating the PF switch, which
> allows link information to be properly provided to VFS in all cases.
>
> Catherine adds driver support for 10GBaseT and bumps driver version.
I've pulled, but I absolutely don't like that change that moved the
variables out of the loop.
Putting variables in the inner-most scope of their use is always the
best choice because:
1) Auditing is easier, because you are constraining the scope in
which you have to check if the variable is setup properly
before it is used.
2) You are helping the compiler out, because you have done the
majority of solving the graph coloring problem for it and the
compiler therefore has less work to do.
Please don't make changes like this in the future, and instead do the
opposite, by moving more variable declarations into their innermost
possible scope.
Thanks.
next prev parent reply other threads:[~2014-10-24 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 4:09 [net-next 0/9][pull request] Intel Wired LAN Driver Updates 2014-10-23 Jeff Kirsher
2014-10-24 4:09 ` [net-next 1/9] i40e: mask phy events Jeff Kirsher
2014-10-24 4:09 ` [net-next 2/9] i40e: enable LSE poke and simplify link state Jeff Kirsher
2014-10-24 4:10 ` [net-next 3/9] i40e/i40evf: Fix whitespace indentation Jeff Kirsher
2014-10-24 4:10 ` [net-next 4/9] i40e/i40evf: Use usleep_range() instead of udelay() Jeff Kirsher
2014-10-24 4:10 ` [net-next 5/9] i40e: Fix a bug where Rx would stop after some time Jeff Kirsher
2014-10-24 4:10 ` [net-next 6/9] i40e: process link events when setting up switch Jeff Kirsher
2014-10-24 4:10 ` [net-next 7/9] i40e: Add 10GBaseT support Jeff Kirsher
2014-10-24 4:10 ` [net-next 8/9] i40e: Moving variable declaration out of the loops Jeff Kirsher
2014-10-24 12:20 ` Sergei Shtylyov
2014-10-24 13:10 ` David Laight
2014-10-24 4:10 ` [net-next 9/9] i40e: Bump version Jeff Kirsher
2014-10-24 20:43 ` David Miller [this message]
2014-10-24 20:45 ` [net-next 0/9][pull request] Intel Wired LAN Driver Updates 2014-10-23 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=20141024.164327.535125094046571848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.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).