[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=YHhRWFix1QDuEnRW7r_UaNtp6KSL9uLdUzdqM@mail.gmail.com>
Date: Mon, 27 Sep 2010 20:38:50 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: "John W. Linville" <linville@...driver.com>
Cc: David Miller <davem@...emloft.net>, sfr@...b.auug.org.au,
netdev@...r.kernel.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (net tree related)
On Mon, Sep 27, 2010 at 8:25 PM, John W. Linville
<linville@...driver.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.
> Seems like the OMAP code needs to select the option
> for this code?
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville@...driver.com might be all we have. Be ready.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists