From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>, netdev@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [RFC PATCH net-next v1 05/11] intel-ethernet: make W=1 build cleanly
Date: Fri, 11 Sep 2020 10:43:48 -0700 [thread overview]
Message-ID: <877dt0nr8r.fsf@intel.com> (raw)
In-Reply-To: <20200911012337.14015-6-jesse.brandeburg@intel.com>
Jesse Brandeburg <jesse.brandeburg@intel.com> writes:
> This takes care of all of the trivial W=1 fixes in the Intel
> Ethernet drivers, which allows developers and maintainers to
> build more of the networking tree with more complete warning
> checks.
>
> Almost all of the changes were trivial comment updates on
> function headers, but some of the changes were for variables that
> were storing a return value from a register read, where the
> return value wasn't used. Those conversions to remove the lvalue
> of the assignment should be safe because the readl memory mapped
> reads are marked volatile and should not be optimized out without
> an lvalue (I suspect a very long time ago this wasn't guaranteed
> as it is today).
>
> Inspired by Lee Jones' series of wireless work to do the same.
> Compile tested only.
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
> drivers/net/ethernet/intel/e100.c | 8 +-
> drivers/net/ethernet/intel/e1000/e1000_hw.c | 147 ++++++++----------
> drivers/net/ethernet/intel/e1000/e1000_main.c | 39 +++--
> .../net/ethernet/intel/e1000e/80003es2lan.c | 1 -
> drivers/net/ethernet/intel/e1000e/ich8lan.c | 16 +-
> drivers/net/ethernet/intel/e1000e/netdev.c | 50 ++++--
> drivers/net/ethernet/intel/e1000e/phy.c | 3 +
> drivers/net/ethernet/intel/e1000e/ptp.c | 2 +-
> drivers/net/ethernet/intel/igb/e1000_82575.c | 6 +-
> drivers/net/ethernet/intel/igb/e1000_i210.c | 5 +-
> drivers/net/ethernet/intel/igb/e1000_mac.c | 1 +
> drivers/net/ethernet/intel/igb/e1000_mbx.c | 1 +
> drivers/net/ethernet/intel/igb/igb_main.c | 28 ++--
> drivers/net/ethernet/intel/igb/igb_ptp.c | 8 +-
> drivers/net/ethernet/intel/igbvf/netdev.c | 17 +-
> drivers/net/ethernet/intel/igc/igc_main.c | 2 +-
> drivers/net/ethernet/intel/igc/igc_ptp.c | 4 +-
> drivers/net/ethernet/intel/ixgb/ixgb_hw.c | 135 ++++++++--------
> drivers/net/ethernet/intel/ixgb/ixgb_main.c | 17 +-
> .../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 3 +-
> 20 files changed, 265 insertions(+), 228 deletions(-)
>
...
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_hw.c b/drivers/net/ethernet/intel/e1000/e1000_hw.c
> index 4e7a0810eaeb..2120dacfd55c 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_hw.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_hw.c
> @@ -139,6 +139,7 @@ static void e1000_phy_init_script(struct e1000_hw *hw)
> * at the end of this routine.
> */
> ret_val = e1000_read_phy_reg(hw, 0x2F5B, &phy_saved_data);
> + e_dbg("Reading PHY register 0x2F5B failed: %d\n", ret_val);
>
Adding this debug statement seems unrelated.
> /* Disabled the PHY transmitter */
> e1000_write_phy_reg(hw, 0x2F5B, 0x0003);
Apart from this,
Reviewed-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
--
Vinicius
next prev parent reply other threads:[~2020-09-11 17:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 1:23 [RFC PATCH net-next v1 00/11] make drivers/net/ethernet W=1 clean Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 01/11] i40e: prepare flash string in a simpler way Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 02/11] i40e: clean up W=1 warnings in i40e Jesse Brandeburg
2020-09-23 2:02 ` [Intel-wired-lan] " Brown, Aaron F
2020-09-11 1:23 ` [RFC PATCH net-next v1 03/11] iavf: clean up W=1 warnings in iavf Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 04/11] ixgbe: clean up W=1 warnings in ixgbe Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 05/11] intel-ethernet: make W=1 build cleanly Jesse Brandeburg
2020-09-11 17:43 ` Vinicius Costa Gomes [this message]
2020-09-11 23:28 ` [Intel-wired-lan] " Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 06/11] drivers/net/ethernet: clean up unused assignments Jesse Brandeburg
2020-09-11 17:16 ` Edward Cree
2020-09-11 1:23 ` [RFC PATCH net-next v1 07/11] drivers/net/ethernet: rid ethernet of no-prototype warnings Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 08/11] drivers/net/ethernet: handle one warning explicitly Jesse Brandeburg
2020-09-11 22:56 ` Jacob Keller
2020-09-11 1:23 ` [RFC PATCH net-next v1 09/11] drivers/net/ethernet: add some basic kdoc tags Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 10/11] drivers/net/ethernet: remove incorrectly formatted doc Jesse Brandeburg
2020-09-11 1:23 ` [RFC PATCH net-next v1 11/11] drivers/net/ethernet: clean up mis-targeted comments Jesse Brandeburg
2020-09-11 17:26 ` Edward Cree
2020-09-11 21:42 ` Jesse Brandeburg
2020-09-11 21:55 ` Edward Cree
2020-09-11 22:26 ` Jakub Kicinski
2020-09-11 23:11 ` Edward Cree
2020-09-12 0:49 ` Jesse Brandeburg
2020-09-14 3:04 ` Andrew Lunn
2020-09-11 14:55 ` [RFC PATCH net-next v1 00/11] make drivers/net/ethernet W=1 clean Jakub Kicinski
2020-09-11 19:00 ` Jesse Brandeburg
2020-09-11 20:12 ` Jakub Kicinski
2020-09-11 21:34 ` Jesse Brandeburg
2020-09-11 22:16 ` Jakub Kicinski
2020-09-11 22:43 ` Vladimir Oltean
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=877dt0nr8r.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@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 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).