public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org,
	Claudio Scordino <claudio@evidence.eu.com>
Subject: Re: On Linux numbering scheme
Date: Sat, 8 Jan 2011 10:31:35 -0800	[thread overview]
Message-ID: <20110108183135.GA22661@kroah.com> (raw)
In-Reply-To: <27552986.2181294505105130.JavaMail.root@mail-zbox20.bo3.lycos.com>

On Sat, Jan 08, 2011 at 11:45:05AM -0500, Artem S. Tashkinov wrote:
> > What userspace scripts/applications expect numbers like that?  How do
> > they handle releases like what Linus just did (2.6.37)?
> > 
> 
> I've just grepped through all the shell scripts installed in Fedora 14 and
> I haven't found any `uname -r` references, so it seems like  the base system
> is quite safe (I haven't tried to grep through binaries as I have no clue
> how to check them).
> 
> However sources of VMWare/NVIDIA/VBox/etc. kernel modules have multiples
> instances of:
> 
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 4, 7)
> #  error This driver does not support 2.4 kernels older than 2.4.7!
> #elif LINUX_VERSION_CODE < KERNEL_VERSION(2, 5, 0)
> #  define KERNEL_2_4
> #elif LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 0)
> #  error This driver does not support 2.5 kernels!
> #elif LINUX_VERSION_CODE < KERNEL_VERSION(2, 7, 0)
> #  define KERNEL_2_6
> #else
> #  error This driver does not support development kernels!
> #endif
> 
> So, it seems like the only obstacle that stops us from starting a completely
> new numbering scheme is proprietary or corporations driven/developed software.

No, those work just fine as well, you need to look at the KERNEL_VERSION
macro to see that.

And any numbering scheme we come up with, will of course be an
incremental number greater than our current number.

But this topic is on hold now until the next kernel summit when it will
be revisited again.  I narrowly missed changing the numbering scheme
last year, hopefully this year will be different.

thanks,

greg k-h

  reply	other threads:[~2011-01-08 18:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18673709.2121294505029740.JavaMail.root@mail-zbox20.bo3.lycos.com>
2011-01-08 16:45 ` On Linux numbering scheme Artem S. Tashkinov
2011-01-08 18:31   ` Greg KH [this message]
2011-01-09 17:38   ` Arnd Bergmann
     [not found] <5600814.270321287742009359.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-22 10:33 ` Artem S. Tashkinov
2010-10-22 10:41   ` Alexey Dobriyan
2010-10-22 11:18     ` Artem S. Tashkinov
2010-10-22 13:25     ` Genes MailLists
2010-10-22 16:51       ` kevin granade
     [not found] <18536664.253751287691209904.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-21 20:02 ` Artem S. Tashkinov
2010-10-22  0:06   ` kevin granade
2010-10-22  2:00     ` Al Viro
2010-10-22  9:53       ` Athanasius
2010-10-22 17:36         ` Bill Davidsen
2010-10-22 21:57       ` Jeremy Fitzhardinge
2010-10-25  9:08       ` Tejun Heo
2010-10-25  9:45         ` Artem S. Tashkinov
2010-10-25  9:56           ` Tejun Heo
2010-10-25 10:04           ` Bernd Petrovitsch
2010-10-25 20:30           ` Nick Bowler
2010-10-26 10:24             ` Dick Streefland
2010-10-26 10:50               ` Martin Nybo Andersen
2011-01-06  8:31   ` Claudio Scordino
2011-01-06  8:59     ` Geert Uytterhoeven
2011-01-08 14:49       ` Artem S. Tashkinov
2011-01-08 16:11         ` Greg KH
2011-01-09 12:54           ` Mark Hounschell

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=20110108183135.GA22661@kroah.com \
    --to=greg@kroah.com \
    --cc=claudio@evidence.eu.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.artem@lycos.com \
    /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