netdev - Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

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

Message-Id: <20110614.143349.1778665510231099747.davem@davemloft.net>
Date:	Tue, 14 Jun 2011 14:33:49 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	vladz@...adcom.com
Cc:	mchan@...adcom.com, bprakash@...adcom.com, eilong@...adcom.com,
	netdev@...r.kernel.org, dmitry@...adcom.com,
	yaniv.rosner@...adcom.com, dwmw2@...radead.org
Subject: Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

From: "Vladislav Zolotarov" <vladz@...adcom.com>
Date: Tue, 14 Jun 2011 11:32:04 -0700

> This requires some sync between Dave and David: David should always
> be the first to integrate a new FW and only then Dave should
> inegrate a driver patch series with the support for this new FW. The
> responsibility for the ordering should be on the driver owner: in
> our case, i shouldn't be sending a net-next patch series until the
> linux-firmware patch is applied.

Ok, then let's get this propagated into David's firmware tree.
--
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