From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John W. Linville" Subject: Re: [PATCH] Staging: agnx: switch config_interface to bss_info_changed Date: Tue, 19 May 2009 10:41:31 -0400 Message-ID: <20090519144131.GB2691@tuxdriver.com> References: <1242127393-4298-1-git-send-email-a.beregalov@gmail.com> <20090512164448.GJ16247@kroah.com> <20090512190254.GB1957@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:53441 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751905AbZESOpP (ORCPT ); Tue, 19 May 2009 10:45:15 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Alexander Beregalov Cc: Greg KH , linux-wireless@vger.kernel.org, gregkh@suse.de, johannes@sipsolutions.net, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org On Tue, May 19, 2009 at 04:12:50PM +0400, Alexander Beregalov wrote: > 2009/5/13 Alexander Beregalov : > > 2009/5/12 Greg KH : > >> On Tue, May 12, 2009 at 09:37:56PM +0400, Alexander Beregalov wrot= e: > >>> 2009/5/12 Greg KH : > >>> > On Tue, May 12, 2009 at 03:23:13PM +0400, Alexander Beregalov w= rote: > >>> >> Fix this build error: > >>> >> drivers/staging/agnx/pci.c: In function 'agnx_config_interface= ': > >>> >> drivers/staging/agnx/pci.c:315: error: dereferencing pointer t= o incomplete type > >>> >> .. > >>> >> drivers/staging/agnx/pci.c:424: error: unknown field 'config_i= nterface' specified in initializer > >>> >> > >>> >> config_interface was removed in 2d0ddec5b2b > >>> >> ("mac80211: unify config_interface and bss_info_changed") > >>> > > >>> > I do not see that patch in Linus's tree. =A0Is it in some other= tree > >>> > (wireless?) and not yet in mainline? > >>> Yes, it is in wireless from linux-next. > >>> You asked to send patches based on linux-next, right? > >>> Should I always mark patches for staging-next tree as [PATCH -nex= t] ? > >> > >> Hm, yes, -staging patches need to be against -next, but I have to = be > >> able to build these somehow on my own without the wireless tree... > >> > >> I think something like this might better go through the wireless t= ree as > >> it depends on changes that happen there. =A0Sound good to you? > > Ok, thanks Greg. > > > >> If so, please send them to the wireless maintainer. > > John, will you apply it? >=20 > John? *grumble* I guess I will... John --=20 John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.