public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@linux.ie>
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: Sat, 9 Oct 2004 21:29:58 -0700	[thread overview]
Message-ID: <20041010042958.GA28025@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410100328080.11219@skynet>

On Sun, Oct 10, 2004 at 03:31:26AM +0100, Dave Airlie wrote:
> 
> I don't want to re-implement kernel modversions which is what we are close
> to doing

Then why not just rely on the modversion code in the kernel tree to do
this?  As you say:

> you can't insmod a module built against a different kernel
> anyways so it doesn't matter, kernel version, preempt, smp, compiler are
> all checked on insmod in 2.6 if they don't match it doesn't load it is not
> possible to distrib a binarry kernel independent module..

Which is a pretty good reason not to try to implement your own
versioning system, right?

> without at least a portable stub source loader...

Are you thinking that someone will try to do this?  If so, they deserve
what they get :)

thanks,

greg k-h

  reply	other threads:[~2004-10-10  4:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 23:54 [RFC] [patch] drm core internal versioning Dave Airlie
2004-10-10  0:52 ` Jon Smirl
2004-10-10  2:31   ` Dave Airlie
2004-10-10  4:29     ` Greg KH [this message]
2004-10-10  5:30       ` Dave Airlie
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=20041010042958.GA28025@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --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