linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: Greg KH <greg@kroah.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Cc: gregkh@suse.de, johannes@sipsolutions.net,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: agnx: switch config_interface to bss_info_changed
Date: Wed, 13 May 2009 00:15:21 +0400	[thread overview]
Message-ID: <a4423d670905121315g503f4f0ep6a60e9051a2aeb9d@mail.gmail.com> (raw)
In-Reply-To: <20090512190254.GB1957@kroah.com>

2009/5/12 Greg KH <greg@kroah.com>:
> On Tue, May 12, 2009 at 09:37:56PM +0400, Alexander Beregalov wrote:
>> 2009/5/12 Greg KH <greg@kroah.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?

  reply	other threads:[~2009-05-12 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 11:23 [PATCH] Staging: agnx: switch config_interface to bss_info_changed Alexander Beregalov
2009-05-12 11:51 ` Alexander Beregalov
2009-05-12 16:44 ` Greg KH
2009-05-12 17:37   ` Alexander Beregalov
2009-05-12 19:02     ` Greg KH
2009-05-12 20:15       ` Alexander Beregalov [this message]
2009-05-19 12:12         ` Alexander Beregalov
2009-05-19 14:41           ` John W. Linville

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4423d670905121315g503f4f0ep6a60e9051a2aeb9d@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).