Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263487AbTICOhE (ORCPT ); Wed, 3 Sep 2003 10:37:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263488AbTICOhE (ORCPT ); Wed, 3 Sep 2003 10:37:04 -0400 Received: from inetc.connecttech.com ([64.7.140.42]:20240 "EHLO inetc.connecttech.com") by vger.kernel.org with ESMTP id S263487AbTICOhC (ORCPT ); Wed, 3 Sep 2003 10:37:02 -0400 From: "Stuart MacDonald" To: , "'James Clark'" Cc: Subject: RE: Driver Model Date: Wed, 3 Sep 2003 10:36:16 -0400 Organization: Connect Tech Inc. Message-ID: <002301c37228$bbc89950$294b82ce@stuartm> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 18 From: linux-kernel-owner@vger.kernel.org > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of > Richard B. Johnson > sources are available. If the driver does not contain the appropriate > MODULE_LICENSE() string, then several tools will show "tainted" so If the MODULE_LICENSE() macro is what determines taint, what's to prevent a company from compiling their driver in their own kernel tree with that macro and releasing it binary-only? Wouldn't that module then be taint-free? ..Stu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/