[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50dd43063e244fa9a4d025873c862331@AcuMS.aculab.com>
Date: Mon, 6 Mar 2023 12:53:24 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'WANG Xuerui' <kernel@...0n.name>,
Huacai Chen <chenhuacai@...nel.org>,
"Xi Ruoyao" <xry111@...111.site>
CC: Huacai Chen <chenhuacai@...ngson.cn>,
Arnd Bergmann <arnd@...db.de>,
"loongarch@...ts.linux.dev" <loongarch@...ts.linux.dev>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
Xuefeng Li <lixuefeng@...ngson.cn>,
Guo Ren <guoren@...nel.org>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"loongson-kernel@...ts.loongnix.cn"
<loongson-kernel@...ts.loongnix.cn>
Subject: RE: [PATCH] LoongArch: Provide kernel fpu functions
...
> Also, if the old world is taken into consideration (which we normally
> have the luxury of not having to do so), consider Ruoyao's case where a
> commercial partner of Loongson wants to do this with the vendor kernel,
> but the symbols are exported GPL -- in this case I doubt the GPL marking
> will remain, thus creating inconsistency between upstream and vendor
> kernels, and community distros are going to complain loudly about the
> need to patch things. It's probably best to avoid all of this upfront.
It is pretty easy to load a non-GPL module into a distro-built
kernel and call GPL-only functions.
(And without doing horrid things with kallsyms.)
As soon as you actually need to do one, adding others isn't a problem.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists