From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 2.6.35-rc1] net-next: vmxnet3 fixes [3/5] Initialize link state at probe time Date: Wed, 14 Jul 2010 14:10:54 -0700 (PDT) Message-ID: <20100714.141054.48510602.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, pv-drivers@vmware.com To: sbhatewara@vmware.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:53650 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404Ab0GNVKj (ORCPT ); Wed, 14 Jul 2010 17:10:39 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Shreyas Bhatewara Date: Tue, 13 Jul 2010 17:48:55 -0700 (PDT) > > Initialize vmxnet3 link state at probe time > > This change initializes the state of link at the time when driver is > loaded. The ethtool output for 'link detected' and 'link speed' > is thus valid even before the interface is brought up. > > Signed-off-by: Shreyas Bhatewara You should never, ever, call netif_start_queue() on a device which has not been brought up. But that is what this patch is doing.