From: David Hollis <dhollis@davehollis.com>
To: Michael Helmling <supermihi@web.de>
Cc: David Brownell <david-b@pacbell.net>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] New, yet unsupported USB-Ethernet adaptor
Date: Wed, 03 May 2006 10:44:48 -0400 [thread overview]
Message-ID: <1146667488.2348.28.camel@dhollis-lnx.sunera.com> (raw)
In-Reply-To: <200605031528.18809.supermihi@web.de>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On Wed, 2006-05-03 at 15:28 +0200, Michael Helmling wrote:
> So, what this Mr. Srihdar di wrong is to set his own name in the "copyright"
> field instead of using yours. The process of modifying a GPLed module itself
> is ok, am I right with this?
> So it should be possible to convince him of this nuisance, and then use the
> changes he made to make moschips device working.
Correct. He is violating the license in a number of ways, though it
probably isn't totally intentional. The development on that driver
probably began before usbnet was modularized to allow for the
componentizing of driver specific code outside of usbnet. What he
should do would be to create a moschip.c that uses usbnet as a support
module - just like asix.c does. In this file, he can have his sole
Copyright attribution and not have to worry about following
changes/updates to usbnet. Of course, if he communicated his
development efforts with the community, he would have received all of
this information long ago and we'd likely help shake out bugs in the
code to make it a more robust driver.
--
David Hollis <dhollis@davehollis.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-03 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 18:02 Michael Helmling
2006-05-02 19:13 ` Ioan Ionita
2006-05-02 20:40 ` Ioan Ionita
2006-05-02 21:03 ` Michael Helmling
[not found] ` <d9def9db0605050554m7b1e093di85782c1b09ca2636@mail.gmail.com>
2006-05-06 21:05 ` Michael Helmling
2006-05-02 21:25 ` Oliver Neukum
2006-05-02 22:09 ` [linux-usb-devel] " David Brownell
2006-05-03 5:06 ` Michael Helmling
2006-05-03 5:29 ` David Brownell
2006-05-03 13:28 ` Michael Helmling
2006-05-03 14:44 ` David Hollis [this message]
2006-05-03 15:31 ` Andrey Panin
2006-05-03 18:14 ` Michael Helmling
2006-05-03 18:33 ` Pavel Machek
2006-05-03 19:10 ` David Brownell
2006-05-03 19:23 ` David Brownell
2006-05-03 18:31 ` Pavel Machek
2006-05-06 23:23 linux
2006-05-08 15:51 ` Markus Rechberger
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=1146667488.2348.28.camel@dhollis-lnx.sunera.com \
--to=dhollis@davehollis.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=supermihi@web.de \
/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
all inboxes | Powered by JetHome®