netdev - [PATCHv2 net-next 0/4] cxgb4: Trivial fixes for cxgb4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Sep 2015 20:33:27 +0530
From:	Hariprasad Shenai <hariprasad@...lsio.com>
To:	netdev@...r.kernel.org
Cc:	davem@...emloft.net, leedom@...lsio.com, nirranjan@...lsio.com,
	Hariprasad Shenai <hariprasad@...lsio.com>
Subject: [PATCHv2 net-next 0/4] cxgb4: Trivial fixes for cxgb4 

Hi,

Fixes the following issues
Don't read non existent T4/T5/T6 adapter registers for ethtool dump.
For T4, dont read mailbox control registers. Adds new devlog faility and
report correct link speed for unsupported ones.

This patch series has been created against net-next tree and includes
patches on cxgb4 driver.

We have included all the maintainers of respective drivers. Kindly review
the change and let us know in case of any review comments.

Thanks

V2: Fix coding style for Patch2/4 ("cxgb4: For T4, don't read the Firmware
 Mailbox Control register") based on review comment by Sergei Shtylyov

Hariprasad Shenai (4):
  cxgb4 : Update T4/T5/T6 register ranges
  cxgb4: For T4, don't read the Firmware Mailbox Control register
  cxgb4: Adds a new Device Log Facility FW_DEVLOG_FACILITY_CF
  cxgb4: Report correct link speed for unsupported ones

 drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c |   19 +-
 drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c    |    6 +-
 drivers/net/ethernet/chelsio/cxgb4/t4_hw.c         | 1464 +++++++++++++++-----
 3 files changed, 1153 insertions(+), 336 deletions(-)

-- 
2.3.4

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html