netdev - [PATCH net-next 0/4] net/mlx4: Mellanox driver update 15-10-2013

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:	Tue, 15 Oct 2013 16:55:20 +0200
From:	Amir Vadai <amirv@...lanox.com>
To:	"David S. Miller" <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, Eyal Perry <eyalpe@...lanox.com>,
	Amir Vadai <amirv@...lanox.com>
Subject: [PATCH net-next 0/4] net/mlx4: Mellanox driver update 15-10-2013

Hi Dave,

This patchset contains small code cleaning patches, and a patch to make
mlx4_core use module_request() in order to load the relevant link layer module
(mlx4_en or mlx4_ib) according to the port type.

Thanks,
Amir

Amir Vadai (1):
  net/mlx4: Unused local variable in mlx4_opreq_action

Eyal Perry (1):
  net/mlx4_core: Load higher level modules according to ports type

Or Gerlitz (2):
  net/mlx4: Clean the code to eliminate trivial build warnings
  net/mlx4: Fix typo, move similar defs to same location

 drivers/net/ethernet/mellanox/mlx4/cmd.c       |  2 --
 drivers/net/ethernet/mellanox/mlx4/en_netdev.c |  2 +-
 drivers/net/ethernet/mellanox/mlx4/fw.c        |  4 +---
 drivers/net/ethernet/mellanox/mlx4/main.c      | 29 ++++++++++++++++++++++++++
 drivers/net/ethernet/mellanox/mlx4/mcg.c       |  6 +++---
 drivers/net/ethernet/mellanox/mlx4/srq.c       |  1 +
 include/linux/mlx4/cmd.h                       |  6 ++----
 include/linux/mlx4/device.h                    |  2 +-
 8 files changed, 38 insertions(+), 14 deletions(-)

-- 
1.8.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