netdev - Re: [net-next 00/36] bnx2x patch series

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 12 Aug 2009 23:09:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eilong@...adcom.com
Cc:	netdev@...r.kernel.org, yanivr@...adcom.com, vladz@...adcom.com,
	gertner@...adcom.com, benli@...adcom.com
Subject: Re: [net-next 00/36] bnx2x patch series

From: "Eilon Greenstein" <eilong@...adcom.com>
Date: Wed, 12 Aug 2009 21:19:22 +0300

> Here is a patch series for the bnx2x. This patch series also replace the
> FW, so
> it contains two big blobs - the new fw and the removal of the old one.
> Those
> patches do not contain anything but the ihex - the actually change to
> the driver
> is in patch number 2 which is small enough to fit the mailing list.
> 
> For those who wish to see all the patches, including the ihex, I also
> updated
> http://linux.broadcom.com/eilong/ to contain this patch series.
> 
> Please consider applying to net-next.

I've applied it all, but sincerely this is absolutely the last
time I'm taking in a patch bomb for a Broadcom ethernet driver.

If it's new stuff, keep it to ~10 patches.

If it's bug fixes outside of the merge window, keep it at
2 or 3 patches.

Post them very near to when you write them, so people have a chance of
actually reviewing your work (I guarentee I am the only non-Broadcom
person who looked over all 36 patches, or who ever will).

"Early and often" as it were...

Thanks.

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