From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: Gabor Juhos <juhosg-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: linux-next: Tree for March 6 (ath9k)
Date: Wed, 11 Mar 2009 10:19:44 -0700 [thread overview]
Message-ID: <49B7F2B0.1000702@oracle.com> (raw)
In-Reply-To: <20090306194045.GE3712-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
John W. Linville wrote:
> On Fri, Mar 06, 2009 at 11:41:02AM -0800, Randy Dunlap wrote:
>> 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...
>
> He just sent it today (or overnight). I'll get it into wireless-next.
>
> John
>
> P.S. I'm starting to think that RFKILL should just be mandatory...
This build error still happens in linux-next-20090311.
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-11 17:19 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
[not found] ` <20090306191311.697e7b97.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-03-06 19:01 ` linux-next: Tree for March 6 (ath9k) Randy Dunlap
[not found] ` <49B17320.8010000-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-03-06 19:35 ` Gabor Juhos
2009-03-06 19:41 ` Randy Dunlap
[not found] ` <49B17C4E.3000004-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-03-06 19:40 ` John W. Linville
[not found] ` <20090306194045.GE3712-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-03-11 17:19 ` Randy Dunlap [this message]
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=49B7F2B0.1000702@oracle.com \
--to=randy.dunlap-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=juhosg-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
/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).