From: Ohad Ben-Cohen <ohad@wizery.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: David Miller <davem@davemloft.net>,
sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (net tree related)
Date: Mon, 27 Sep 2010 21:01:08 +0200 [thread overview]
Message-ID: <AANLkTi=2KqQb+gvuigxb+-tSzawx7=q3HtnkkE6t_4XF@mail.gmail.com> (raw)
In-Reply-To: <20100927184445.GF11086@tuxdriver.com>
On Mon, Sep 27, 2010 at 8:44 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Mon, Sep 27, 2010 at 08:38:50PM +0200, Ohad Ben-Cohen wrote:
>> On Mon, Sep 27, 2010 at 8:25 PM, John W. Linville
>> <linville@tuxdriver.com> wrote:
>> >> BTW, if this fuglet going to work if the driver is built modular?
>> >>
>> >> The idea of this things seems to be to allow arch platform code to call
>> >> into it to set things. Such calls from arch platform code are going
>> >> to be "obj-y"
>> >>
>> >> So if this is built into the modular driver, I can't see how it
>> >> can work.
>> >
>> > Dave is right -- these Kconfig dependencies (or lack thereof) seem
>> > to be wrong.
>>
>> This is why I had to put it in drivers/net/wireless/Makefile (in both
>> the original patch and in the fix I sent earlier) and not in
>> drivers/net/wireless/wl12xx/Makefile (as it was in the fix that Dave
>> was referring to).
>>
>> This way it works with a modular driver.
>
> That doesn't seem very helpful if someone selects
>
> CONFIG_MACH_OMAP_ZOOM2=y
> CONFIG_WL12XX_PLATFORM_DATA=n
>
CONFIG_WL12XX_PLATFORM_DATA is selected automatically if the relevant
driver is selected (this is independent of the underlying arch/board):
config WL12XX_PLATFORM_DATA
bool
depends on WL1271_SDIO != n
default y
All we have to make sure is that it will be compiled built-in. If we
use drivers/net/wireless/wl12xx/Makefile, and we build a modular
wl1271_sdio, it won't (despite it being selected as y).
That's why I put it in drivers/net/wireless/Makefile.
In the original patch I put the code itself in
drivers/net/wireless/wl12xx to make it look nicer, but as Stephen
reported that seem to break building with a separate object folder...
So the fix I sent just moves that builtin code to
drivers/net/wireless. This maintains the builtin property even if the
driver is modular, and fixes the issue reported by Stephen.
Please tell me if you have any thoughts/suggestions.
Thanks,
Ohad.
> or am I missing something?
>
> 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:[~2010-09-27 19:01 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 5:44 linux-next: build failure after merge of the final tree (net tree related) Stephen Rothwell
2010-09-27 8:17 ` David Miller
2010-09-27 15:55 ` Ohad Ben-Cohen
2010-09-27 18:04 ` John W. Linville
2010-09-27 18:18 ` David Miller
2010-09-27 18:25 ` John W. Linville
2010-09-27 18:38 ` Ohad Ben-Cohen
2010-09-27 18:44 ` John W. Linville
2010-09-27 19:01 ` Ohad Ben-Cohen [this message]
2010-09-27 19:06 ` Ohad Ben-Cohen
2010-09-27 19:44 ` John W. Linville
2010-09-27 20:18 ` Ohad Ben-Cohen
-- strict thread matches above, loose matches on Subject: below --
2012-01-09 5:38 Stephen Rothwell
2012-01-09 6:52 ` David Miller
2012-01-16 7:36 ` Glauber Costa
2011-12-22 6:07 Stephen Rothwell
2011-12-22 6:16 ` Eric Dumazet
2011-12-22 7:01 ` David Miller
2011-11-02 5:37 Stephen Rothwell
2011-11-02 5:50 ` David Miller
2011-08-15 5:20 Stephen Rothwell
2011-08-15 5:56 ` David Miller
2011-08-16 5:28 ` Stephen Rothwell
2011-08-16 6:11 ` David Miller
2011-08-16 6:57 ` Stephen Rothwell
2011-08-16 7:17 ` David Miller
2011-06-23 5:29 Stephen Rothwell
2011-06-23 13:04 ` Alexey Dobriyan
2011-06-27 5:29 ` Stephen Rothwell
2011-06-29 6:09 ` Stephen Rothwell
2011-06-29 9:58 ` David Miller
2011-06-23 5:25 Stephen Rothwell
2011-06-27 5:35 ` Stephen Rothwell
2011-06-29 6:01 ` Stephen Rothwell
2011-06-29 9:56 ` David Miller
2011-06-08 5:54 Stephen Rothwell
2011-06-08 7:16 ` David Miller
2011-04-21 22:10 Stephen Rothwell
2011-04-21 22:19 ` David Miller
2011-02-03 4:13 Stephen Rothwell
2011-02-03 4:46 ` David Miller
2011-02-03 5:14 ` Stephen Rothwell
2010-11-15 0:46 Stephen Rothwell
2010-11-15 16:52 ` David Miller
2010-11-15 16:58 ` Eric Dumazet
2010-10-18 7:36 Stephen Rothwell
2010-10-18 8:06 ` David Miller
2010-09-03 1:47 Stephen Rothwell
2010-09-03 1:52 ` Stephen Rothwell
2010-09-03 2:16 ` David Miller
2010-09-03 2:14 ` David Miller
2010-08-31 3:18 Stephen Rothwell
2010-08-31 4:43 ` David Miller
2010-08-30 3:04 Stephen Rothwell
2010-08-30 3:29 ` Simon Horman
2010-08-30 4:23 ` David Miller
2010-08-25 2:09 Stephen Rothwell
2010-08-25 4:22 ` Rasesh Mody
2010-08-25 7:35 ` David Miller
2010-08-25 20:59 ` David Miller
2010-08-25 21:53 ` Rasesh Mody
2010-08-26 1:05 ` Stephen Rothwell
2010-08-23 3:27 Stephen Rothwell
2010-08-23 3:31 ` David Miller
2010-07-29 4:13 Stephen Rothwell
2010-07-29 5:21 ` David Miller
2010-04-27 5:25 Stephen Rothwell
2010-04-27 16:34 ` David Miller
2010-04-27 17:18 ` David Miller
2010-04-28 1:11 ` Stephen Rothwell
2010-03-29 6:43 Stephen Rothwell
2010-03-29 6:52 ` Eric Dumazet
2010-03-29 6:59 ` Eric Dumazet
2010-03-29 8:01 ` David Miller
2010-03-29 8:04 ` Stephen Rothwell
2010-03-29 7:01 ` Stephen Rothwell
2010-03-18 4:23 Stephen Rothwell
2010-03-18 6:23 ` David Miller
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='AANLkTi=2KqQb+gvuigxb+-tSzawx7=q3HtnkkE6t_4XF@mail.gmail.com' \
--to=ohad@wizery.com \
--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).