From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Vlad Zolotarov" <vladz@broadcom.com>
Subject: Pushing the new FW to firmware git
Date: Mon, 23 May 2011 18:12:59 +0300
Message-ID: <201105231813.00751.vladz@broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "David Woodhouse" <dwmw2@infradead.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mms3.broadcom.com ([216.31.210.19]:3170 "EHLO MMS3.broadcom.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754839Ab1EWPNa (ORCPT <rfc822;netdev@vger.kernel.org>);
	Mon, 23 May 2011 11:13:30 -0400
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

David, could u, pls., clarify about the exact procedure of pushing the new FW 
to the  firwmware git: when exactly the new firware is going to be fetched to 
the kernel tree? 

I'm asking it because I am going to submit a patch that introduces a new FW 
and the new code will simply not work with an old FW.

Thanks in advance,
vlad