netdev - Re: [ofa-general][PATCH 2/2] mlx4: ConnectX multi functional device support

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-prev] [day] [month] [year] [list]

Date:	Sun, 05 Jul 2009 11:10:13 +0300
From:	Tziporet Koren <tziporet@....mellanox.co.il>
To:	Roland Dreier <rdreier@...co.com>
CC:	Tziporet Koren <tziporet@....mellanox.co.il>,
	netdev@...r.kernel.org, general@...ts.openfabrics.org,
	davem@...emloft.net
Subject: Re: [ofa-general][PATCH 2/2] mlx4: ConnectX multi functional device
 support

Roland Dreier wrote:
>  
> Well, I need to think over the patch a little more.  The risk is
> certainly not zero, since we are changing device initialization for all
> mlx4 devices.  And I'm not sure if missing 2.6.31 support is that big a
> deal for you, is it?  How many users do you have building their own
> upstream kernels?  You're just going to tell everyone to use OFED
> anyway, right?
>   
This is NOT related to OFED at all. This is our 10G NIC driver. See the 
description:

/* MT26468 ConnectX EN 10GigE, PCIe, 2.0 5Gt/s */

We have several customer that take our 10G driver from kernel.org, and 
once the HW is out we will have a problem.
Also to include this code in next Redhat & Novell updates we need to 
have it in the kernel too.

I know the risk is not zero, but you must admit its not high either, and 
we already tested it here thoroughly here with all device IDs
Since we sent the patches on time for inclusion not clear why they are 
being declined now.
Please see what can be done.

Thanks,
Tziporet
--
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