public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Whitwell <keithw@valinux.com>
To: Rik Faith <faith@valinux.com>
Cc: DRI Development <dri-devel@lists.sourceforge.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Dri-devel] DRM patch for Linux 2.4.0-prerelease
Date: Thu, 04 Jan 2001 14:27:22 -0700	[thread overview]
Message-ID: <3A54EABA.EB3FBF7C@valinux.com> (raw)
In-Reply-To: <14932.51363.118932.987520@light.alephnull.com>

Rik,

It looks like this patch goes further than syncing with xfree 4.0.2, but syncs
with the dri trunk instead.  There has been a version bump in the mga drm
module on the dri trunk to add a 'blit' ioctl.  XFree 4.0.2 will barf on this.

As a broader question:  All our version checking (in client drivers and DDX
drivers) check

	found major == expected major
	found minor == expected minor 
	found patch >= expected patch

and if they don't receive this, they refuse to play.

As I understood it, the major number is bumped on backwards-incompatible
changes, the minor number on backwards-compatible changes and the patch on all
other changes, though in practise never.

Thus, wouldn't the appropriate test be:

	found major == expected major
	found minor >= expected minor
	(no test on patch)

This seems to match the semantics of the 3 numbers better?

Keith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2001-01-04 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14932.51363.118932.987520@light.alephnull.com>
2001-01-04 21:27 ` Keith Whitwell [this message]
2001-01-04 21:53   ` [Dri-devel] DRM patch for Linux 2.4.0-prerelease Rik Faith

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=3A54EABA.EB3FBF7C@valinux.com \
    --to=keithw@valinux.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=faith@valinux.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