Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

2019-01-15 Thread Kash Pande
On 2019-01-15 5:42 a.m., Greg Kroah-Hartman wrote: > On Tue, Jan 15, 2019 at 02:01:48PM +0100, Rene Schickbauer wrote: >> To be frank, your argument, which boils down to "GPL is the only correct >> open source license", makes me ashamed to have been advocating people >> switching to Linux. This is

Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

2019-01-15 Thread Kash Pande
> Yes, the "GPL condom" attempt doesn't work at all.  It's been shot down > a long time ago in the courts. SFLC maintains there is no kernel licensing issue[1]. As a side note, even Hellwig's suit against VMware was dismissed (he may appeal)[2]. Debian and Canonical base their decision to ship

Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

2019-01-10 Thread Kash Pande
On 2019-01-10 9:40 p.m., Greg Kroah-Hartman wrote: > Sorry, no, we do not keep symbols exported for no in-kernel users. > > greg k-h Hi Greg, Can you please address the email that Lukas was responding to? Thanks. signature.asc Description: OpenPGP digital signature

Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

2019-01-10 Thread Kash Pande
> Yes, the "GPL condom" attempt doesn't work at all.  It's been shot down > a long time ago in the courts. SFLC maintains there is no kernel licensing issue[1]. As a side note, even Hellwig's suit against VMware was dismissed (he may appeal)[2]. Debian and Canonical base their decision to ship

Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

2019-01-10 Thread Kash Pande
> On Thu, Jan 10, 2019 at 07:07:52PM +0100, Sebastian Andrzej Siewior wrote: > > On 2019-01-10 17:32:58 [+], Hutter, Tony wrote: > > > > But since when did out-of-tree modules use __kernel_fpu_begin?  It's an > > > > x86-only thing, and shouldn't really be used by anyone, right? > > > > > >

it87 removal from github pending

2018-07-09 Thread Kash Pande
Just thought a notice would be appropriate here that groeck has decided to discontinue work on his it87 driver due to difficulties upstreaming it, which is a shame, because it is the only working version of the driver. https://github.com/groeck/it87/blob/master/README Kash Pande

it87 removal from github pending

2018-07-09 Thread Kash Pande
Just thought a notice would be appropriate here that groeck has decided to discontinue work on his it87 driver due to difficulties upstreaming it, which is a shame, because it is the only working version of the driver. https://github.com/groeck/it87/blob/master/README Kash Pande

Re: [PATCH 4.14 000/109] 4.14.28-stable review

2018-03-26 Thread Kash Pande
On 2018-03-19 02:20 PM, Guenter Roeck wrote: > Ryzen and Threadripper are only supported in v4.15+. Nope, the offset for 1900X is not available in 4.15, I've had to manually patch all systems otherwise monitoring complains they idle at 53C. signature.asc Description: OpenPGP digital

Re: [PATCH 4.14 000/109] 4.14.28-stable review

2018-03-26 Thread Kash Pande
On 2018-03-19 02:20 PM, Guenter Roeck wrote: > Ryzen and Threadripper are only supported in v4.15+. Nope, the offset for 1900X is not available in 4.15, I've had to manually patch all systems otherwise monitoring complains they idle at 53C. signature.asc Description: OpenPGP digital

Re: [PATCH 4.14 000/109] 4.14.28-stable review

2018-03-19 Thread Kash Pande
gt; > Responses should be made by Sun Mar 18 15:22:53 UTC 2018. > Anything received after that time might be too late. Any chance to get the k10temp change for Threadripper 1900X offset reporting included [https://patchwork.kernel.org/patch/10175457/]? Kash Pande signature.asc Descrip

Re: [PATCH 4.14 000/109] 4.14.28-stable review

2018-03-19 Thread Kash Pande
gt; > Responses should be made by Sun Mar 18 15:22:53 UTC 2018. > Anything received after that time might be too late. Any chance to get the k10temp change for Threadripper 1900X offset reporting included [https://patchwork.kernel.org/patch/10175457/]? Kash Pande signature.asc Descrip