From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Luis R. Rodriguez" <lrodriguez@atheros•com>
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: Tue, 12 Aug 2008 13:33:54 +1000 [thread overview]
Message-ID: <20080812133354.2eadf82d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080811164657.GE6128@tesla>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Hi Luis,
On Mon, 11 Aug 2008 09:46:57 -0700 "Luis R. Rodriguez" <lrodriguez@atheros•com> wrote:
>
> On Sun, Aug 10, 2008 at 11:20:40PM -0700, Stephen Rothwell wrote:
> >
> > 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.
>
> 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.
That is only the first application of the patch, my patch is a fix of a
second instance of the same code. See Adrian's post.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-12 3:34 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 ` ath9k build failure Luis R. Rodriguez
2008-08-11 18:52 ` Adrian Bunk
2008-08-12 3:33 ` Stephen Rothwell [this message]
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=20080812133354.2eadf82d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Luis.Rodriguez@Atheros$(echo .)com \
--cc=Sujith.Manoharan@Atheros$(echo .)com \
--cc=bunk@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=lrodriguez@atheros$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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