From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: linux-next: wireless-current tree build failure
Date: Wed, 22 Apr 2009 09:03:56 -0400 [thread overview]
Message-ID: <20090422130356.GA3288@tuxdriver.com> (raw)
In-Reply-To: <20090422151928.d1c5ad6a.sfr@canb.auug.org.au>
On Wed, Apr 22, 2009 at 03:19:28PM +1000, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> drivers/net/wireless/iwlwifi/iwl3945-base.c:1415: error: __ksymtab_iwl3945_rx_queue_reset causes a section type conflict
>
> I am pretty sure that this is a compiler bug, so not to worry. However,
> as far as I can see, iwl-3945.o (the only user) and iwl3945-base.o are
> always linked into the same module, so the EXPORT_SYMBOL (which causes
> the problem) should not be needed. Correct?
>
> I applied the following patch for today. This makes the above error go
> away and my x86_64 allmodconfig still builds.
Seems reasonable. Reinette, should I just take Stephen's patch?
Or would you prefer some other solution?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-04-22 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 5:19 linux-next: wireless-current tree build failure Stephen Rothwell
2009-04-22 13:03 ` John W. Linville [this message]
2009-04-22 18:08 ` reinette chatre
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 6:21 Stephen Rothwell
2008-08-05 15:37 ` Adrian Bunk
2008-08-05 16:00 ` John W. Linville
2008-08-05 16:35 ` Stephen Rothwell
2008-08-05 16:02 ` Stephen Rothwell
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=20090422130356.GA3288@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-next@vger.kernel.org \
--cc=reinette.chatre@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.