From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761465AbZBLXLq (ORCPT ); Thu, 12 Feb 2009 18:11:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758227AbZBLXLi (ORCPT ); Thu, 12 Feb 2009 18:11:38 -0500 Received: from mx2.suse.de ([195.135.220.15]:56059 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756825AbZBLXLh (ORCPT ); Thu, 12 Feb 2009 18:11:37 -0500 Date: Thu, 12 Feb 2009 15:08:46 -0800 From: Greg KH To: David Miller Cc: greg@kroah.com, randy.dunlap@oracle.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 9/9] staging/sxg: fix napi interface build Message-ID: <20090212230846.GA25058@suse.de> References: <20090211132256.6622afb5.randy.dunlap@oracle.com> <20090212195133.GB16214@kroah.com> <20090212.145620.268233419.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090212.145620.268233419.davem@davemloft.net> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 12, 2009 at 02:56:20PM -0800, David Miller wrote: > From: Greg KH > Date: Thu, 12 Feb 2009 11:51:33 -0800 > > > On Wed, Feb 11, 2009 at 01:22:56PM -0800, Randy Dunlap wrote: > > > From: Randy Dunlap > > > > > > Fix staging/sxg napi interface calls: > > > > > > drivers/staging/sxg/sxg.c:1271: error: implicit declaration of function 'netif_rx_schedule_prep' > > > linux-next-20090209/drivers/staging/sxg/sxg.c:1272: error: implicit declaration of function '__netif_rx_schedule' > > > drivers/staging/sxg/sxg.c:1325: error: implicit declaration of function 'netif_rx_complete' > > > > As I count over 80 instances of netif_rx_complete in Linus's tree right > > now, I'm guesing this is due to a change from the netdev tree. Which is > > fine, but I'll wait until that gets merged with Linus to apply this > > patch. > > Well it means that it won't build in -next until the next merge > window. I can live with that :) Or is the new api already there and it's safe to make this change now? thanks, greg k-h