public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Alex Lyashkov <umka@sevcity.net>
Cc: Giuliano Pochini <pochini@shiny.it>,
	alex@alexfisher.me.uk, linux-kernel@vger.kernel.org,
	"Jeff V. Merkey" <jmerkey@utah-nac.org>,
	Michael Buesch <mbuesch@freenet.de>
Subject: Re: Would I be violating the GPL?
Date: Wed, 02 Nov 2005 15:29:38 +0000	[thread overview]
Message-ID: <87fyqfm5jx.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1130943242.3367.39.camel@berloga.shadowland> (Alex Lyashkov's message of "2 Nov 2005 14:55:14 -0000")

On 2 Nov 2005, Alex Lyashkov moaned:
>> > So despite the fact the driver has been written in c++, it
>> > might be possible to write a usable specification.
>> 
>> Linux 2.6 doesn't accept c++, so you have to rewrite it anyway.
>> You should ask them if you can publish your own driver based
>> on infos you extract from their driver.
>> 
> without exeption c++ code can be used at drivers.

The rather important `struct class' may give you trouble there.

-- 
`"Gun-wielding recluse gunned down by local police" isn't the epitaph
 I want. I am hoping for "Witnesses reported the sound up to two hundred
 kilometers away" or "Last body part finally located".' --- James Nicoll

  reply	other threads:[~2005-11-02 15:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 17:49 Would I be violating the GPL? Alexander Fisher
2005-11-01 16:43 ` Jeff V. Merkey
2005-11-01 19:15   ` Alistair John Strachan
2005-11-16 15:26     ` David Schwartz
2005-11-16 16:39       ` Jeffrey V. Merkey
2005-11-01 20:32   ` Rob Landley
2005-11-01 20:46   ` Arjan van de Ven
2005-11-01 19:00 ` Michael Buesch
2005-11-01 17:44   ` Jeff V. Merkey
2005-11-01 19:12     ` Michael Buesch
2005-11-01 20:46       ` Alexander Fisher
2005-11-01 21:06         ` linux-os (Dick Johnson)
2005-11-02  9:49         ` Giuliano Pochini
2005-11-02 14:54           ` Alex Lyashkov
2005-11-02 15:29             ` Nix [this message]
2005-11-02 15:42               ` Alex Lyashkov
2005-11-02 16:16               ` linux-os (Dick Johnson)
2005-11-02 17:26                 ` Nix
2005-11-02 15:55             ` Giuliano Pochini
2005-11-10 19:02           ` Jan Engelhardt
2005-11-10 19:12             ` Lennart Sorensen
2005-11-17 21:23               ` Jan Engelhardt
2005-11-18 15:19                 ` Lennart Sorensen
2005-11-18 15:25                   ` Jan Engelhardt
2005-11-18 21:55                   ` Petr Vandrovec
2005-11-01 22:04     ` Rob Landley
2005-11-01 19:58   ` Lee Revell
2005-11-01 20:30     ` Jeff V. Merkey
2005-11-01 20:57     ` Alexander Fisher
2005-11-02 16:12 ` Stuart MacDonald
2005-11-03 12:44 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 22:21 linux
2005-11-02 22:47 ` linux-os (Dick Johnson)
2005-11-03  3:50 ` Rob Landley
2005-11-04  0:57   ` Horst von Brand

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=87fyqfm5jx.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=alex@alexfisher.me.uk \
    --cc=jmerkey@utah-nac.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    --cc=pochini@shiny.it \
    --cc=umka@sevcity.net \
    /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