All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: fix modular legacy build errors
Date: Thu, 18 Nov 2010 11:55:09 -0800	[thread overview]
Message-ID: <4CE5849D.1060705@oracle.com> (raw)
In-Reply-To: <1290109607.3801.8.camel@jlt3.sipsolutions.net>

On 11/18/10 11:46, Johannes Berg wrote:
> On Thu, 2010-11-18 at 11:29 -0800, Randy Dunlap wrote:
> 
>> It's listed as being part of the linux-next pull, so I guess that there is still
>> some sort of config/build problem.
>>
>> Same linker errors as above.  Here is today's config file that causes the error (attached).
>>
>>
>> CONFIG_IWLWIFI=m
>> CONFIG_IWLWIFI_DEBUG=y
>> # CONFIG_IWLWIFI_DEBUG_EXPERIMENTAL_UCODE is not set
>> # CONFIG_IWLAGN is not set
>> CONFIG_IWL3945=m
> 
> Yeah, it's a bit confusing .. I'm pretty sure I tried all this when
> doing the non-5000+ patch. Can you try adding
> 
> iwlcore-objs += $(iwlcore-m)
> 
> to your Makefile after the iwl-legacy lines and see if that helps for
> you as well? It seems that the reason is that iwl-legacy never gets

Yes, that builds fine.

> added because it's -m?

Seems so.

> But then why did iwlagn-$(CONFIG_IWL4965) and iwl3945-$(CONFIG_IWL3945)
> work for you? That bit confuses me completely. It looks like this should
> be working? I mean -- why doesn't iwl-legacy.c now get compiled, but
> does if you move it to agn like you did here:
> 
> 
> -iwlagn-$(CONFIG_IWL4965) += iwl-4965.o
> +iwlagn-$(CONFIG_IWL4965) += iwl-4965.o iwl-legacy.o
> 
> Why does that work, but not iwlcore-$(CONFIG_IWL4965)??

I dunno, but I only tested my erroneous patch when building as loadable
modules, not builtin.  Testing error on my part.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-11-18 19:56 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
2010-11-18 19:29             ` Randy Dunlap
2010-11-18 19:46               ` Johannes Berg
2010-11-18 19:55                 ` Randy Dunlap [this message]
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=4CE5849D.1060705@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.