linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH -next] wireless: TI wlxxx depends on MAC80211
Date: Fri, 11 May 2012 00:36:17 +0300	[thread overview]
Message-ID: <1336685777.12189.142.camel@cumari.coelho.fi> (raw)
In-Reply-To: <4FAC3249.3060107@xenotime.net>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hey Randy,

On Thu, 2012-05-10 at 14:25 -0700, Randy Dunlap wrote:
> On 05/03/2012 05:55 AM, Luciano Coelho wrote:
> 
> > On Mon, 2012-04-16 at 12:51 -0700, Randy Dunlap wrote:
> >> From: Randy Dunlap <rdunlap@xenotime.net>
> >>
> >> wl12xx build fails with many undefined symbol errors when MAC80211
> >> and CFG80211 are not enabled, so make WLCORE and WL12XX depend
> >> on MAC80211 (which already depends on CFG80211).
> >>
> >> Here are a few of the many build errors:

[...]

> >> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> >> Cc:	Luciano Coelho <coelho@ti.com>
> >> Cc:	linux-wireless@vger.kernel.org
> >> Cc:	"John W. Linville" <linville@tuxdriver.com>
> >> ---
> > 
> > Applied! Thanks Randy, and sorry for the delay in pushing this through
> > my tree.
> 
> 
> 
> Ping.
> 
> This patch is still needed in linux-next of 20120510.

I already applied this patch and sent a pull-request to Linville, but he
hasn't pulled from my tree into wireless-next yet.

Would it make sense for you to pull directly from my tree into
linux-next?

-- 
Cheers,
Luca.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-10 21:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  6:11 linux-next: Tree for Apr 16 Stephen Rothwell
2012-04-16 19:50 ` [PATCH -next] mtd: fix sbc2_flash build when PCI is not enabled Randy Dunlap
2012-04-16 22:20   ` Paul Gortmaker
2012-04-17  1:25     ` Randy Dunlap
2012-04-25 11:05   ` Artem Bityutskiy
2012-04-25 15:33   ` Artem Bityutskiy
2012-04-16 19:51 ` [PATCH -next] wireless: TI wlxxx depends on MAC80211 Randy Dunlap
2012-04-17  5:30   ` Luciano Coelho
2012-04-17 18:29     ` Randy Dunlap
2012-04-17 15:52       ` Luciano Coelho
     [not found]   ` <4F8C784B.2040402-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-05-03 12:55     ` Luciano Coelho
2012-05-10 21:25       ` Randy Dunlap
2012-05-10 21:36         ` Luciano Coelho [this message]
2012-05-10 21:37           ` Randy Dunlap
2012-05-11 11:59   ` Arend van Spriel
2012-04-17  1:01 ` [PATCH -next] staging: fix android alarm.c printk format warnings Randy Dunlap
2012-04-17  1:01 ` [PATCH -next] soc: fix printk format in soc-dapm.c Randy Dunlap
2012-04-16 22:52   ` [alsa-devel] " Fabio Estevam
2012-04-17  1:01 ` [PATCH -next] hippi: fix printk format in rrunner.c Randy Dunlap
2012-04-17  3:48   ` David Miller

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=1336685777.12189.142.camel@cumari.coelho.fi \
    --to=coelho@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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).