public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christopher Turcksin <turcksin@raleigh.ibm.com>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Proper way to release binary driver?
Date: Sat, 07 Apr 2001 12:06:22 +0100	[thread overview]
Message-ID: <3ACEF4AE.DBCDDD@raleigh.ibm.com> (raw)
In-Reply-To: <EFC879D09684D211B9C20060972035B1D46A39@exchange2ca.sv.dialogic.com> <m1g0fnwoo0.fsf@frodo.biederman.org> <3ACDE5C5.CEB65D4A@raleigh.ibm.com>

Hello,



I would like to thank everybody who replied to my question yesterday.
There were a lot of good suggestions and examples for me to go and look
at.

The conclusion we had come to between ourselves here was already very
similar to most things suggested, but we were running into some smaller
problems that would make our release too difficult to use for most
customers.

And ofcourse, I have no realised that it is not enough to simply release
your code under GPL. You need to tie in with the real kernel as soon as
you can.

Thanks again all for your help.


-- 
bfn,
wabbit

IBM Global Services, UK AMS in Greenock, Scotland.

	" To err is human, but to really foul things up requires the root
password. "

  parent reply	other threads:[~2001-04-07 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05 10:58 Proper way to release binary-only driver? Miller, Brendan
2001-04-05 11:50 ` Eric W. Biederman
2001-04-06 15:50   ` Proper way to release binary driver? Christopher Turcksin
2001-04-06 16:09     ` Joel Jaeggli
2001-04-06 16:22     ` J . A . Magallon
2001-04-07  1:24     ` How to build modules outside the kernel tree? [Was: Proper way to release binary driver?] Eric W. Biederman
2001-04-08 13:10       ` Jamie Lokier
2001-04-07  8:18     ` Proper way to release binary driver? Alan Cox
2001-04-09 13:11       ` Henning P. Schmiedehausen
2001-04-07 11:06     ` Christopher Turcksin [this message]
2001-04-06  5:33 ` Proper way to release binary-only driver? 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=3ACEF4AE.DBCDDD@raleigh.ibm.com \
    --to=turcksin@raleigh.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox