Some VF registers are using PF's name by mistake.
Although the addresses of the VF's and PF's are the same,
we should use the right names.

Fixes: 0198848a47f5 ("ixgbe: add access to specific device info")

Signed-off-by: Wenzhuo Lu <wenzhuo.lu at intel.com>
---
 drivers/net/ixgbe/ixgbe_regs.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/net/ixgbe/ixgbe_regs.h b/drivers/net/ixgbe/ixgbe_regs.h
index 4af035f..ca4725d 100644
--- a/drivers/net/ixgbe/ixgbe_regs.h
+++ b/drivers/net/ixgbe/ixgbe_regs.h
@@ -56,10 +56,10 @@ static const struct reg_info ixgbe_regs_general[] = {
 };

 static const struct reg_info ixgbevf_regs_general[] = {
-       {IXGBE_CTRL, 1, 1, "IXGBE_CTRL"},
-       {IXGBE_STATUS, 1, 1, "IXGBE_STATUS"},
+       {IXGBE_VFCTRL, 1, 1, "IXGBE_VFCTRL"},
+       {IXGBE_VFSTATUS, 1, 1, "IXGBE_VFSTATUS"},
        {IXGBE_VFLINKS, 1, 1, "IXGBE_VFLINKS"},
-       {IXGBE_FRTIMER, 1, 1, "IXGBE_FRTIMER"},
+       {IXGBE_VFFRTIMER, 1, 1, "IXGBE_VFFRTIMER"},
        {IXGBE_VFMAILBOX, 1, 1, "IXGBE_VFMAILBOX"},
        {IXGBE_VFMBMEM, 16, 4, "IXGBE_VFMBMEM"},
        {IXGBE_VFRXMEMWRAP, 1, 1, "IXGBE_VFRXMEMWRAP"},
-- 
1.9.3

Reply via email to