netdev - Re: [PATCH 00/41]bnx2x: enhancements and clean up for net-next

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]

Message-Id: <20090215.233609.86653297.davem@davemloft.net>
Date:	Sun, 15 Feb 2009 23:36:09 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	eilong@...adcom.com
Cc:	netdev@...r.kernel.org, yanivr@...adcom.com,
	harvey.harrison@...il.com
Subject: Re: [PATCH 00/41]bnx2x: enhancements and clean up for net-next

From: "Eilon Greenstein" <eilong@...adcom.com>
Date: Thu, 12 Feb 2009 20:36:03 +0200

> Finally, an enhancement patch for the bnx2x. Due to many reasons (among
> which FW stability and chasing some bugs) it took a while to stabilize
> and the longer it took the longer the list got. So unfortunately, this
> is a long list - hopefully for the last time. I realize that sending a
> too many patches together is bad practice and I will do my best to avoid
> it in the future.

You're lucky I'm in a really good mood today :-)

> The first patch is a new FW patch. It is way too big for the mailing
> list, but I'm hoping you will get it directly to your mailbox. This
> patch has very little review value since it is simply the new FW blob,
> FW header file renames and the mandatory driver renames to accommodate
> it.
> 
> Please consider applying to net-next.

Ok, everything is applied to net-next-2.6 and pushed out to kernel.org

Please followup with patches for Ben Hutchings's feedback, as you
promised you would.

Thank you.
--
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