diff --git a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html index 408314af4b48035f167dba5e45ce2ab29f7806b4..d2691fb25d72119452d982a2e77d83fd9cb73bab 100644 --- a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html +++ b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html @@ -156,8 +156,7 @@ Code, and for which (at least some) source code for which is provided.

Conservancy examined the incomplete CCS alongside the binary “vmkernel” component. Such examination indicates that function in “vmkernel” do make function calls to Linux's kernel code - in the usual way for a single program written in C.

-

+ in the usual way for a single program written in C.

Doesn't VMware's “shim layer” insulate them from GPL obligations and allow them to keep certain code in their kernel