From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Hisashi T Fujinaka <htodd@twofifty.com>
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>,
Matthew Vick <matthew.vick@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Mitch Williams <mitch.a.williams@intel.com>,
Linux NICS <linux.nics@intel.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000: remove unused variables
Date: Thu, 27 Nov 2014 18:37:25 +0530 [thread overview]
Message-ID: <20141127130725.GA12406@sudip-PC> (raw)
In-Reply-To: <alpine.NEB.2.11.1411262157110.1481@chris.i8u.org>
On Wed, Nov 26, 2014 at 09:59:28PM -0800, Hisashi T Fujinaka wrote:
> I'm pretty sure those double reads are there for a reason, so most of
> this I'm going to have to check on Monday. We have a long holiday
> weekend here in the US.
if the double reads are there for some reason, can you please let me know what that reason might be..
>
> I'm not sure why you're bothering with an old driver like this, but if
> you haven't actually tried this on all the hardware it pertains to, I'm
> going want to NAK this.
no it has not been tested on hardware. :(
i am still in the learning process, NAK is also part of learning.
infact there is another part of the code, which, theoretically, will never get executed. but i didnot dare to send that removal patch without testing on the hardware.
thanks
sudip
>
> I should do this from my todd.fujinaka@intel.com account but it's 10PM
> on the first day of a long holiday weekend.
>
> On Thu, 27 Nov 2014, Sudip Mukherjee wrote:
>
> >these variables were only being assigned some values, but were never
> >used.
> >
> >Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> >---
> >drivers/net/ethernet/intel/e1000/e1000_hw.c | 142 ++++++++++++--------------
<snip>
> > case SPEED_100:
> >- txb2b = false;
> > /* maybe add some timeout factor ? */
> > break;
> > }
> >
>
> --
> Hisashi T Fujinaka - htodd@twofifty.com
> BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee
next prev parent reply other threads:[~2014-11-27 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 5:22 [PATCH] e1000: remove unused variables Sudip Mukherjee
2014-11-27 5:22 ` Sudip Mukherjee
2014-11-27 5:59 ` Hisashi T Fujinaka
2014-11-27 13:07 ` Sudip Mukherjee [this message]
2014-11-28 23:28 ` Florian Fainelli
2014-11-28 23:28 ` Florian Fainelli
2014-11-29 11:01 ` Lino Sanfilippo
2014-11-29 11:01 ` Lino Sanfilippo
2014-11-30 1:45 ` Ben Hutchings
2014-11-30 1:45 ` Ben Hutchings
2014-12-01 4:54 ` Sudip Mukherjee
2014-12-01 4:54 ` Sudip Mukherjee
2014-12-01 18:56 ` [linux-nics] " Fujinaka, Todd
2014-12-02 14:24 ` Sudip Mukherjee
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=20141127130725.GA12406@sudip-PC \
--to=sudipm.mukherjee@gmail.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=htodd@twofifty.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=matthew.vick@intel.com \
--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 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.