From: Lino Sanfilippo <LinoSanfilippo@gmx•de>
To: Florian Fainelli <f.fainelli@gmail•com>,
Sudip Mukherjee <sudipm.mukherjee@gmail•com>,
Hisashi T Fujinaka <htodd@twofifty•com>
Cc: Linux NICS <linux.nics@intel•com>,
e1000-devel@lists•sourceforge.net,
Bruce Allan <bruce.w.allan@intel•com>,
Jesse Brandeburg <jesse.brandeburg@intel•com>,
linux-kernel@vger•kernel.org,
John Ronciak <john.ronciak@intel•com>,
netdev@vger•kernel.org
Subject: Re: [PATCH] e1000: remove unused variables
Date: Sat, 29 Nov 2014 12:01:03 +0100 [thread overview]
Message-ID: <5479A76F.5050809@gmx.de> (raw)
In-Reply-To: <54790537.809@gmail.com>
On 29.11.2014 00:28, Florian Fainelli wrote:
> Also, if you do a read that is not stored in any return value, the
> compiler is now free to remove that actual read,
This does not apply to reads from iomem (see "volatile" specifier in
readl()).
Regards,
Lino
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2014-11-29 11:01 UTC|newest]
Thread overview: 9+ 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:59 ` Hisashi T Fujinaka
2014-11-27 13:07 ` Sudip Mukherjee
2014-11-28 23:28 ` Florian Fainelli
2014-11-29 11:01 ` Lino Sanfilippo [this message]
2014-11-30 1:45 ` Ben Hutchings
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=5479A76F.5050809@gmx.de \
--to=linosanfilippo@gmx$(echo .)de \
--cc=bruce.w.allan@intel$(echo .)com \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=htodd@twofifty$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=john.ronciak@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux.nics@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sudipm.mukherjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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