public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "David S. Miller" <davem@davemloft•net>,
	Johannes Berg <johannes@sipsolutions•net>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: net/wireless/wireless-current tree build warning
Date: Mon, 7 Dec 2009 17:32:37 -0500	[thread overview]
Message-ID: <20091207223236.GF18939@tuxdriver.com> (raw)
In-Reply-To: <20091208092057.dd2eeaeb.sfr@canb.auug.org.au>

On Tue, Dec 08, 2009 at 09:20:57AM +1100, Stephen Rothwell wrote:
> Hi Dave, John,
> 
> On Mon, 07 Dec 2009 14:15:54 +0100 Johannes Berg <johannes@sipsolutions•net> wrote:
> >
> > > drivers/net/wireless/iwlwifi/iwl-tx.c: In function 'iwl_tx_agg_stop':
> > > drivers/net/wireless/iwlwifi/iwl-tx.c:1356: warning: passing argument 1 of 'ieee80211_stop_tx_ba_cb_irqsafe' from incompatible pointer type
> > > include/net/mac80211.h:2128: note: expected 'struct ieee80211_vif *' but argument is of type 'struct ieee80211_hw *'
> > 
> > This has now snuck into wireless-testing as well.
> 
> Johannes is right, the patch I posted need to be part of the wireless
> tree once the wireless-current tree was merged into it.  Now this patch
> (reposted below) is needed in the wireless and net trees ...

I've just merged such a patch...thanks!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver•com			might be all we have.  Be ready.

  reply	other threads:[~2009-12-07 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01  2:35 linux-next: net/wireless/wireless-current tree build warning Stephen Rothwell
2009-12-01  9:14 ` Johannes Berg
2009-12-07 13:15 ` Johannes Berg
2009-12-07 22:20   ` Stephen Rothwell
2009-12-07 22:32     ` John W. Linville [this message]
2009-12-07 22:59       ` Stephen Rothwell
2009-12-07 23:19         ` David Miller
2009-12-08  0:20           ` Stephen Rothwell

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=20091207223236.GF18939@tuxdriver.com \
    --to=linville@tuxdriver$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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