From: Jim Crilly <jim@why.dont.jablowme.net>
To: linux-kernel@vger.kernel.org
Cc: bugfixer@lists.ru
Subject: Re: 2.6.12-rc1-mm3: class_simple API
Date: Mon, 28 Mar 2005 02:45:30 -0500 [thread overview]
Message-ID: <20050328074530.GD11458@mail> (raw)
In-Reply-To: <20050327183927.GA4535@nikolas.hn.org>
On 03/27/05 01:39:27PM -0500, Nick Orlov wrote:
> On Sun, Mar 27, 2005 at 10:17:17AM -0800, Greg KH wrote:
> > On Sun, Mar 27, 2005 at 01:04:31PM -0500, Nick Orlov wrote:
> > >
> > > - Whether the changes like the one above are "the right thing to do" ?
> >
> > Yes.
>
> Questionable.
>
> >
> > > - What's the best way to deal with this particular issue ?
> >
> > Change the code to not use these functions.
>
> In other words "forget about nvidia <-> udev interaction" ?
> I do not think it is acceptable.
>
> > Look at the vmware code for examples of how to do this.
>
> Is there a place where I can download the code example without
> registering / paying license fee ?
http://ftp.cvut.cz/vmware/
The file vmware-any-any-update*.tar.gz contains the source to all of the
VMWare kernel modules. IIRC I found the URL in the VMWare newsgroups and
they're maintained unofficially by a VMWare employee.
>
> P.S. Please CC me, I'm not subscribed to the list.
>
> --
> With best wishes,
> Nick Orlov.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-03-28 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 18:04 2.6.12-rc1-mm3: class_simple API Nick Orlov
2005-03-27 18:17 ` Greg KH
2005-03-27 18:39 ` Nick Orlov
2005-03-28 7:45 ` Jim Crilly [this message]
2005-03-31 3:19 ` Valdis.Kletnieks
2005-03-31 4:16 ` Nick Orlov
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=20050328074530.GD11458@mail \
--to=jim@why.dont.jablowme.net \
--cc=bugfixer@lists.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.