[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AF233D1473C1364ABD51D28909A1B1B75C17F4D4@pgsmsx114.gar.corp.intel.com>
Date: Thu, 20 Jun 2019 03:14:29 +0000
From: "Ong, Boon Leong" <boon.leong.ong@...el.com>
To: Andrew Lunn <andrew@...n.ch>,
"Voon, Weifeng" <weifeng.voon@...el.com>
CC: "David S. Miller" <davem@...emloft.net>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jose Abreu <joabreu@...opsys.com>,
"Giuseppe Cavallaro" <peppe.cavallaro@...com>,
Florian Fainelli <f.fainelli@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
"Gomes, Vinicius" <vinicius.gomes@...el.com>
Subject: RE: [RFC net-next 1/5] net: stmmac: introduce IEEE 802.1Qbv
configuration functionalities
>> > It looks like most o the TSN_WARN should actually be netdev_dbg().
>> >
>> > Andrew
>>
>> Hi Andrew,
>> This file is targeted for dual licensing which is GPL-2.0 OR BSD-3-Clause.
>> This is the reason why we are using wrappers around the functions so that
>> all the function call is generic.
>
>I don't see why dual licenses should require wrappers. Please explain.
>
> Thanks
> Andrew
Agree with the Andrew. We can change those wrapper functions that have
serve the internal development needs for multiple OS scaling reason.
We will update the kernel codes as suggsted.
Powered by blists - more mailing lists