From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: Sasha Neftin <sasha.neftin@intel.com>,
netdev@vger.kernel.org, sassmann@redhat.com,
anthony.l.nguyen@intel.com, Gal Hammer <ghammer@redhat.com>
Subject: [PATCH net-next 10/15] igc: Fix TDBAL register show incorrect value
Date: Wed, 3 Feb 2021 16:42:54 -0800 [thread overview]
Message-ID: <20210204004259.3662059-11-anthony.l.nguyen@intel.com> (raw)
In-Reply-To: <20210204004259.3662059-1-anthony.l.nguyen@intel.com>
From: Sasha Neftin <sasha.neftin@intel.com>
Fixed a typo which caused the registers dump function to read the
RDBAL register when printing TDBAL register values.
_reg_dump method has been partially derived from i210 and have
same typo.
Suggested-by: Gal Hammer <ghammer@redhat.com>
Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
---
drivers/net/ethernet/intel/igc/igc_dump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/igc/igc_dump.c b/drivers/net/ethernet/intel/igc/igc_dump.c
index 4b9ec7d0b727..495bed47ed0a 100644
--- a/drivers/net/ethernet/intel/igc/igc_dump.c
+++ b/drivers/net/ethernet/intel/igc/igc_dump.c
@@ -75,7 +75,7 @@ static void igc_regdump(struct igc_hw *hw, struct igc_reg_info *reginfo)
break;
case IGC_TDBAL(0):
for (n = 0; n < 4; n++)
- regs[n] = rd32(IGC_RDBAL(n));
+ regs[n] = rd32(IGC_TDBAL(n));
break;
case IGC_TDBAH(0):
for (n = 0; n < 4; n++)
--
2.26.2
next prev parent reply other threads:[~2021-02-04 0:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 0:42 [PATCH net-next 00/15][pull request] 1GbE Intel Wired LAN Driver Updates 2021-02-03 Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 01/15] igc: Clean up nvm_operations structure Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 02/15] igc: Remove igc_set_fw_version comment Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 03/15] igc: Remove MULR mask define Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 04/15] igc: Add Host Good Packets Transmitted Count Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 05/15] igc: Expose the NVM version Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 06/15] igc: Expose the gPHY firmware version Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 07/15] igc: Prefer strscpy over strlcpy Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 08/15] igc: Remove unused local receiver mask Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 09/15] igc: Remove unused FUNC_1 mask Tony Nguyen
2021-02-04 0:42 ` Tony Nguyen [this message]
2021-02-04 0:42 ` [PATCH net-next 11/15] igb: fix TDBAL register show incorrect value Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 12/15] igb: Enable RSS for Intel I211 Ethernet Controller Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 13/15] igb: remove h from printk format specifier Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 14/15] e1000e: remove the redundant value assignment in e1000_update_nvm_checksum_spt Tony Nguyen
2021-02-04 0:42 ` [PATCH net-next 15/15] e1000: drop unneeded assignment in e1000_set_itr() Tony Nguyen
2021-02-05 5:40 ` [PATCH net-next 00/15][pull request] 1GbE Intel Wired LAN Driver Updates 2021-02-03 patchwork-bot+netdevbpf
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=20210204004259.3662059-11-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=ghammer@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.neftin@intel.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).