From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"David S. Miller" <davem@davemloft.net>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Sujith Manoharan <Sujith.Manoharan@Atheros.com>
Subject: Re: ath9k build failure
Date: Mon, 11 Aug 2008 09:46:57 -0700 [thread overview]
Message-ID: <20080811164657.GE6128@tesla> (raw)
In-Reply-To: <20080811162040.ed7b8ab7.sfr@canb.auug.org.au>
On Sun, Aug 10, 2008 at 11:20:40PM -0700, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> drivers/net/wireless/ath9k/hw.c: In function 'ath9k_hw_spur_mitigate':
> drivers/net/wireless/ath9k/hw.c:4925: internal compiler error: in expand_expr_real_1, at expr.c:9199
>
> This is a driver that is in Linus' tree and has no patches in the
> linux-next tree.
>
> The original work around talked about applying the patch twice, so I
> applied the below patch.
Stephen,
this is also in wireless-testing. I also see this in linux-2.6
under b08cbcd4546445740c2a04291204b56f8baf7be2. Not sure how this didn't
get through linux-next.
Luis
next parent reply other threads:[~2008-08-11 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080811162040.ed7b8ab7.sfr@canb.auug.org.au>
2008-08-11 16:46 ` Luis R. Rodriguez [this message]
2008-08-11 18:52 ` ath9k build failure Adrian Bunk
2008-08-12 3:33 ` Stephen Rothwell
2008-08-12 13:21 ` 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=20080811164657.GE6128@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Sujith.Manoharan@Atheros.com \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--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).