linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bourne <jbourne@hardrock.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Martin Schlemmer <azarah@gentoo.org>,
	Ken Brownfield <brownfld@irridia.com>,
	Marc-Christian Petersen <m.c.p@wolk-project.de>,
	KML <linux-kernel@vger.kernel.org>
Subject: Re: Oops: ptrace fix buggy
Date: Mon, 14 Apr 2003 12:16:13 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0304141133370.24506-100000@cafe.hardrock.org> (raw)
In-Reply-To: <20030414172111.GI10347@wohnheim.fh-wedel.de>

On Mon, 14 Apr 2003, Jörn Engel wrote:

> On Mon, 14 April 2003 11:09:02 -0600, James Bourne wrote:
> > 
...
> > will need to be looked at as these are ones which contain references to
> > SUBVERSION...  References to EXTRAVERSION also reside in these files.  It
> > would just be better to do the "right thing" IMHO.
> > 
> > I will take a look at this and produce a patch for the same.
> 
> Ok. But the patch I lost really didn't do anything else and works for
> me (TM).
> 
> joern@Limerick:~$ uname -a
> Linux Limerick 2.4.20.1-je1 #3 Sun Apr 6 22:20:45 CEST 2003 i686 unknown unknown GNU/Linux
> joern@Limerick:~$ 

Hi,
The problem comes in when you bump the FIXLEVEL for example, by one.  At
that point the LINUX_VERSION_CODE would not change even though you have a
new kernel and modules compiled for the previous version may not load or
may load and not work correctly (just one example).

EXTRAVERSION on the other hand is not used for LINUX_VERSION_CODE
calculation.  

Regards
James Bourne

> Jörn

-- 
James Bourne                  | Email:            jbourne@hardrock.org          
Unix Systems Administrator    | WWW:           http://www.hardrock.org
Custom Unix Programming       | Linux:  The choice of a GNU generation
----------------------------------------------------------------------
 "All you need's an occasional kick in the philosophy." Frank Herbert  


  reply	other threads:[~2003-04-14 18:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 12:22 Oops: ptrace fix buggy Michael Lampe
2003-04-12  7:13 ` Ken Brownfield
2003-04-12  9:54   ` Marc-Christian Petersen
2003-04-14 13:34     ` James Bourne
2003-04-14 13:46       ` Jörn Engel
2003-04-14 13:56         ` James Bourne
2003-04-14 14:22           ` Jörn Engel
2003-04-14 14:31         ` Martin Schlemmer
2003-04-14 14:47           ` Jörn Engel
2003-04-14 17:09             ` James Bourne
2003-04-14 17:21               ` Jörn Engel
2003-04-14 18:16                 ` James Bourne [this message]
2003-04-14 17:50               ` Russell King
2003-04-14 18:10             ` Martin Schlemmer
2003-04-14 18:58               ` Jörn Engel
2003-04-14 19:20                 ` Valdis.Kletnieks
2003-04-14 21:19                 ` James Bourne
2003-04-14 21:41                   ` Jörn Engel
2003-04-15  6:10                   ` Martin Schlemmer
2003-04-15  6:00                 ` Martin Schlemmer

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.44.0304141133370.24506-100000@cafe.hardrock.org \
    --to=jbourne@hardrock.org \
    --cc=azarah@gentoo.org \
    --cc=brownfld@irridia.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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;
as well as URLs for NNTP newsgroup(s).