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 =EDrta:
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Linus' release of -rc7 seems to have stirred people up a bit ...
>>>
>>> Changes since 20090305:
>>
>> when CONFIG_RFKILL=3Dn, ath9k/virtual.c causes:
>>
>> (.text+0x224e83): undefined reference to `ath_radio_disable'
>> (.text+0x224e8b): undefined reference to `ath_radio_enable'
>>
>>
>=20
> Hi,
>=20
> I have submitted a patch for this already:
> http://marc.info/?l=3Dlinux-wireless&m=3D123633468314970&w=3D2
>=20
> Should I send it to somewhere else as well?
It hasn't propagated into the linux-next merging yet...
--=20
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-06 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090306191311.697e7b97.sfr@canb.auug.org.au>
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
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 \
/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).