From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Greg KH <greg@kroah.com>, Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-mm1, class_simple_* and GPL addition
Date: Wed, 27 Oct 2004 23:21:07 +0200 [thread overview]
Message-ID: <20041027212107.GA22957@vana.vc.cvut.cz> (raw)
In-Reply-To: <1098906941.6990.30.camel@laptop.fenrus.org>
On Wed, Oct 27, 2004 at 09:55:41PM +0200, Arjan van de Ven wrote:
> On Wed, 2004-10-27 at 21:17 +0200, Petr Vandrovec wrote:
> > VMware's vmnet is broken by this too. VMware was asked by RedHat to
> > add udev compatibility to the code, and now you are saying that both
>
> who in Red Hat (notice the space) asked you this? I'm not aware of any
> official request to vmware to do this...
I assumed that email I received from Warren Togami was official notice that
RHEL4 is going to be udev based and that as vmnet does not currently create
its device nodes in /dev, something should be done about it.
As this request was quite popular, and doing it properly through sysfs
instead of doing several mknods when initscripts run, I filled internal
bug report that RHEL4 will use udev and vmnet should be compatible with
it. And then I implemented some minimal sysfs support.
Week after that I saw first email from Greg changing sysfs_driver_* & co.
to GPL only. I did not worry as this set did not comtain class_simple,
and so I assumed that I'm doing nothing wrong. But today I noticed
that even class_simple is GPL only in -mm.
It was not lot of work, I'd say under 1 hour, but it just does not seem
correct to me, changing symbols visibility after people start using them.
OK, next beta will do several mknods in /etc/init.d/vmware script.
Not technically nice, but working.
Petr Vandrovec
next prev parent reply other threads:[~2004-10-27 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 13:50 Norbert Preining
2004-10-27 15:37 ` Greg KH
[not found] ` <1098890583.6990.20.camel@laptop.fenrus.org>
2004-10-27 17:08 ` Norbert Preining
2004-10-27 19:17 ` Petr Vandrovec
2004-10-27 19:55 ` Arjan van de Ven
2004-10-27 21:21 ` Petr Vandrovec [this message]
2004-10-28 1:12 ` Dmitry Torokhov
2004-10-29 20:55 ` Greg KH
2004-10-29 22:06 ` Petr Vandrovec
2004-10-30 11:44 ` Dave Airlie
2004-10-30 14:44 ` Fabio Coatti
2004-11-01 22:31 ` Greg KH
2004-11-09 23:12 ` Luke Maurer
2004-11-10 10:32 ` Fabio Coatti
2004-12-16 17:50 ` Chris Wright
2004-12-16 18:57 ` Greg KH
2004-10-27 21:30 ` Dave Airlie
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=20041027212107.GA22957@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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®