From: Dave Airlie <airlied@linux.ie>
To: Greg KH <greg@kroah.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [patch] drm core internal versioning..
Date: Sun, 10 Oct 2004 06:30:56 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0410100625220.12189@skynet> (raw)
In-Reply-To: <20041010042958.GA28025@kroah.com>
>
> Then why not just rely on the modversion code in the kernel tree to do
> this? As you say:
well that's what I hope to do, I'd just like to stop people doing the
basic silly thing of insmodding a personality on a core built from a
different tree...
the main reason I can't rely on CONFIG_MODVERSIONS is in my Fedora install
at least: CONFIG_MODVERSIONS is not set so it is of no use if it is
optional...
> Which is a pretty good reason not to try to implement your own
> versioning system, right?
excactly that's why I just want to do the simple thing that I posted as
opposed to Jons scheme that increases version numbers and things
depending on builds... I don't think we need that, the problem we are
trying to solve is that of someone taking an external DRM tree, building
it and trying to only use the personality modules.. for us this is a
support issue we deal with the mails.. someone like ATI is still free for
example to do it, they can build their module against the current kernel
core code and all will be okay... and if there is any issues they are paid
to deal with it...
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person
next prev parent reply other threads:[~2004-10-10 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 23:54 Dave Airlie
2004-10-10 0:52 ` Jon Smirl
2004-10-10 2:31 ` Dave Airlie
2004-10-10 4:29 ` Greg KH
2004-10-10 5:30 ` Dave Airlie [this message]
2004-10-10 6:44 ` Arjan van de Ven
2004-10-10 7:00 ` Dave Airlie
2004-10-12 1:46 ` Ian Romanick
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=Pine.LNX.4.58.0410100625220.12189@skynet \
--to=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=jonsmirl@gmail.com \
--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 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®