From: "John W. Linville" <linville@tuxdriver.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: fix modular legacy build errors
Date: Thu, 18 Nov 2010 12:54:34 -0500 [thread overview]
Message-ID: <20101118175434.GC2468@tuxdriver.com> (raw)
In-Reply-To: <1290101760.6131.1.camel@wwguy-ubuntu>
On Thu, Nov 18, 2010 at 09:36:00AM -0800, Guy, Wey-Yi wrote:
> John,
>
> On Thu, 2010-11-18 at 09:11 -0800, Randy Dunlap wrote:
> > On Wed, 17 Nov 2010 09:11:16 -0800 Guy, Wey-Yi wrote:
> >
> > > Hi Randy,
> > >
> > > On Wed, 2010-11-17 at 09:12 -0800, Randy Dunlap wrote:
> > > > On 11/17/10 08:49, Johannes Berg wrote:
> > > > > On Wed, 2010-11-17 at 08:36 -0800, Guy, Wey-Yi wrote:
> > > > >> Hi Randy,
> > > > >>
> > > > >> the "iwlwifi: fix modular legacy build errors" patch cause the following
> > > > >> WARNING when compile
> > > > >
> > > > > I thought we already had had a fix for that issue anyway?
> > > >
> > > > Not that I know of. I reported a different build error and
> > > > included a patch, which is now causing problems, so I asked
> > > > John to drop/revert my patch.
> > > >
> > > > Here is part of the patch description that I sent:
> > > >
> > > >
> > > > With CONFIG_IWLWIFI=m, CONFIG_IWLAGN=m, and CONFIG_IWL3945=m,
> > > > a kernel build has errors as below. Changing a few lines in the
> > > > Makefile is one possible fix for these build errors.
> > > >
> > > > ERROR: "iwl_legacy_mac_config" [drivers/net/wireless/iwlwifi/iwl3945.ko] undefined!
> > > > ERROR: "iwl_isr_legacy" [drivers/net/wireless/iwlwifi/iwl3945.ko] undefined!
> > > > ERROR: "iwl_legacy_tx_cmd_protection" [drivers/net/wireless/iwlwifi/iwl3945.ko] undefined!
> > > > ERROR: "iwl_legacy_mac_bss_info_changed" [drivers/net/wireless/iwlwifi/iwl3945.ko] undefined!
> > > > ERROR: "iwl_legacy_mac_reset_tsf" [drivers/net/wireless/iwlwifi/iwl3945.ko] undefined!
> > > >
> > > >
> > > > So John can revert my patch and then let the iwlwifi maintainers fix this problem,
> > > > please.
> > > >
> > >
> > > "iwlagn: fix non-5000+ build" send by Johannes should have this problem
> > > addressed.
> >
> >
> > Can we get this patch into linux-next, please?
> > linux-next of 2010.1118 is still having these build errors.
> >
>
> Could you help?
It's in wireless-next-2.6 already. Has linux-next stopped pulling that?
--
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:[~2010-11-18 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:36 iwlwifi: fix modular legacy build errors Guy, Wey-Yi
2010-11-17 16:49 ` Johannes Berg
2010-11-17 17:12 ` Randy Dunlap
2010-11-17 17:11 ` Guy, Wey-Yi
2010-11-18 17:11 ` Randy Dunlap
2010-11-18 17:36 ` Guy, Wey-Yi
2010-11-18 17:54 ` John W. Linville [this message]
2010-11-18 19:29 ` Randy Dunlap
2010-11-18 19:46 ` Johannes Berg
2010-11-18 19:55 ` Randy Dunlap
2010-11-18 20:03 ` Johannes Berg
2010-11-17 17:06 ` Please revert "iwlwifi: fix modular legacy build errors" patch Guy, Wey-Yi
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=20101118175434.GC2468@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=wey-yi.w.guy@intel.com \
/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).