linux-kernel - Re: linux-next: Tree for March 6 (ath9k)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090311181935.GD8761@tuxdriver.com>
Date:	Wed, 11 Mar 2009 14:19:36 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Gabor Juhos <juhosg@...nwrt.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: linux-next: Tree for March 6 (ath9k)

On Wed, Mar 11, 2009 at 10:19:44AM -0700, Randy Dunlap wrote:
> 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.

That fix is in wireless-next-2.6 as of yesterday.  I guess it was a
little too late for yesterday's linux-next build -- sorry!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/