All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-ac2
Date: Thu, 11 Sep 2003 14:33:41 -0700	[thread overview]
Message-ID: <20030911213341.GE26618@matchmail.com> (raw)
In-Reply-To: <bjqoo7$tp5$1@gatekeeper.tmr.com>

On Thu, Sep 11, 2003 at 09:16:55PM +0000, Bill Davidsen wrote:
> In article <200309092334.h89NYxh18536@devserv.devel.redhat.com>,
> Alan Cox  <alan@redhat.com> wrote:
> | (No its not course start time quite yet..)
> | 
> | Various little fixups and tidying bits. Some of these probably want to
> | get pushed on to Marcelo eventually - the small bits and the CMPCI update
> | certainly.
> | 
> | Linux 2.4.22-ac2
> | o	Taint on sii6512 module that someone 		(Arjan van de Ven)
> | 	"accidentally" marked as GPL but is nonfree
> 
> I'm happy to say I haven't ever had to use a tainted kernel, but is this
> clearly marked at config time? Should there be a USE_TAINTED_CODE
> global, like the EXPERIMENTAL and BROKEN options?

Is this "module" in the kernel tree?

If it is, how does it live there at all?  Maybe it's an Open Source license,
that lets you distribute the code, but because of incompatabilities has to
be built as a module?

  reply	other threads:[~2003-09-11 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 23:34 Linux 2.4.22-ac2 Alan Cox
2003-09-10  0:02 ` Erik Steffl
2003-09-10  1:51 ` Gerardo Exequiel Pozzi
2003-09-11 21:16 ` bill davidsen
2003-09-11 21:33   ` Mike Fedyk [this message]
2003-09-11 21:41     ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030911213341.GE26618@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.