From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: a3load.hex
Date: Mon, 17 Oct 2005 18:45:33 +0000 [thread overview]
Message-ID: <20051017184533.GA2416@kroah.com> (raw)
In-Reply-To: <20051014134617.42227.qmail@web30703.mail.mud.yahoo.com>
On Mon, Oct 17, 2005 at 06:14:51AM -0700, william baroniunas wrote:
> Thanks for you reply.
>
> I am not actually giving advice, but seeking it. My
> concern is that there are many distributions that
> include this module,
Which distros are they?
> and unless we get Cypress to rewrite their copyright, that leaves the
> door open for litigation.
They did rewrite it. Have you looked at the version in our cvs tree:
http://cvs.sourceforge.net/viewcvs.py/linux-hotplug/fxload/a3load.hex?rev=1.1&view=auto
What is wrong with that?
> I am going to try to work with them to have this
> license updated for the open source community, but
> that's a long shot.
David already did that. See the above file please.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-10-17 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 13:46 a3load.hex william baroniunas
2005-10-14 21:13 ` a3load.hex Greg KH
2005-10-15 17:27 ` a3load.hex Adrian McMenamin
2005-10-17 13:14 ` a3load.hex william baroniunas
2005-10-17 18:45 ` Greg KH [this message]
2005-10-17 18:59 ` a3load.hex Adrian McMenamin
2005-10-17 19:57 ` a3load.hex Darren Salt
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=20051017184533.GA2416@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).