[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13c83500-0fd3-9376-f03a-715949287b84@ti.com>
Date: Thu, 25 Apr 2019 09:44:39 -0400
From: Murali Karicheri <m-karicheri2@...com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Grygorii Strashko <grygorii.strashko@...com>
CC: <netdev@...r.kernel.org>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
"David S . Miller" <davem@...emloft.net>,
Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>, Sekhar Nori <nsekhar@...com>,
<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>
Subject: Re: [PATCH net-next 02/19] net: ethernet: ti: cpsw: drop
TI_DAVINCI_CPDMA config option
Jakub,
On 04/23/2019 08:27 PM, Jakub Kicinski wrote:
> On Tue, 23 Apr 2019 16:08:53 +0300, Grygorii Strashko wrote:
>> Both drivers CPSW and EMAC can't work without CPDMA, hence simplify build
>> of those drivers by always linking davinci_cpdma and drop TI_DAVINCI_CPDMA
>> config option.
>> Note. the davinci_emac driver module was changed to "ti_davinci_emac" to
>> make build work.
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
>
> Last time I tried including the same object file in two different
> modules it backfired pretty badly. Would you mind sparing some
> details as to why you need to do this?
>
How did you get to know they backfired? make allmodconfig will catch the
issue??
Murali
Powered by blists - more mailing lists