linux-kernel - Re: [PATCH] Staging: agnx: switch config_interface to bss_info

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

Date:	Tue, 19 May 2009 10:41:31 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Alexander Beregalov <a.beregalov@...il.com>
Cc:	Greg KH <greg@...ah.com>, linux-wireless@...r.kernel.org,
	gregkh@...e.de, johannes@...solutions.net,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: agnx: switch config_interface to
	bss_info_changed

On Tue, May 19, 2009 at 04:12:50PM +0400, Alexander Beregalov wrote:
> 2009/5/13 Alexander Beregalov <a.beregalov@...il.com>:
> > 2009/5/12 Greg KH <greg@...ah.com>:
> >> On Tue, May 12, 2009 at 09:37:56PM +0400, Alexander Beregalov wrote:
> >>> 2009/5/12 Greg KH <greg@...ah.com>:
> >>> > On Tue, May 12, 2009 at 03:23:13PM +0400, Alexander Beregalov wrote:
> >>> >> Fix this build error:
> >>> >> drivers/staging/agnx/pci.c: In function 'agnx_config_interface':
> >>> >> drivers/staging/agnx/pci.c:315: error: dereferencing pointer to incomplete type
> >>> >> ..
> >>> >> drivers/staging/agnx/pci.c:424: error: unknown field 'config_interface' 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.  Is 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 -next] ?
> >>
> >> 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 tree as
> >> it depends on changes that happen there.  Sound good to you?
> > Ok, thanks Greg.
> >
> >> If so, please send them to the wireless maintainer.
> > John, will you apply it?
> 
> John?

*grumble*

I guess I will...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/