LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: linux-next: Tree for March 6 (ath9k)
Date: Fri, 06 Mar 2009 11:41:02 -0800	[thread overview]
Message-ID: <49B17C4E.3000004@oracle.com> (raw)
In-Reply-To: <49B17B12.3050200@openwrt.org>

Gabor Juhos wrote:
> Randy Dunlap írta:
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Linus' release of -rc7 seems to have stirred people up a bit ...
>>>
>>> Changes since 20090305:
>>
>> when CONFIG_RFKILL=n, ath9k/virtual.c causes:
>>
>> (.text+0x224e83): undefined reference to `ath_radio_disable'
>> (.text+0x224e8b): undefined reference to `ath_radio_enable'
>>
>>
> 
> Hi,
> 
> I have submitted a patch for this already:
> http://marc.info/?l=linux-wireless&m=123633468314970&w=2
> 
> Should I send it to somewhere else as well?

It hasn't propagated into the linux-next merging yet...


-- 
~Randy

  reply	other threads:[~2009-03-06 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  8:13 linux-next: Tree for March 6 Stephen Rothwell
2009-03-06 19:01 ` linux-next: Tree for March 6 (ath9k) Randy Dunlap
2009-03-06 19:35   ` Gabor Juhos
2009-03-06 19:41     ` Randy Dunlap [this message]
2009-03-06 19:40       ` John W. Linville
2009-03-11 17:19         ` Randy Dunlap
2009-03-11 18:19           ` John W. Linville
2009-03-06 19:24 ` linux-next: Tree for March 6 Andrew Morton
2009-03-10  5:47   ` Stephen Rothwell
2009-03-06 21:24 ` [PATCH -next] dvb/frontends: fix duplicate 'debug' symbol Randy Dunlap
2009-03-06 23:59   ` Andrew Morton
2009-03-07  0:05     ` Randy Dunlap

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=49B17C4E.3000004@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=juhosg@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for March 6 (ath9k)' \
    /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

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).