public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamal Mostafa <kamal@canonical.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>,
	Luis Henriques <luis.henriques@canonical.com>
Subject: Re: [PATCH] Makefile: version.h macros KERNEL_EXTRAVERSION, LINUX_EXTRAVERSION_CODE
Date: Fri, 20 Jun 2014 08:47:58 -0700	[thread overview]
Message-ID: <1403279278.14743.64.camel@fourier> (raw)
In-Reply-To: <53A4016E.9040108@suse.cz>

On Fri, 2014-06-20 at 11:39 +0200, Michal Marek wrote:
> Dne 19.6.2014 16:44, Kamal Mostafa napsal(a):
> > Adds new macro KERNEL_EXTRAVERSION(a,b,c,d) and value
> > LINUX_EXTRAVERSION_CODE to version.h, allowing ranged version checks of
> > extended-stable versions that use a numeric EXTRAVERSION value.
> > 
> > The new KERNEL_EXTRAVERSION(a,b,c,d) works like KERNEL_VERSION(a,b,c)...
> > If EXTRAVERSION is set to ".{integer}" (the common extended-stable kernel
> > version number scheme) then {integer} corresponds to KERNEL_EXTRAVERSION's
> > fourth arg.  If EXTRAVERSION is blank or a non-".{integer}" string like
> > "-rc5", that corresponds to a fourth parameter of 0.
> 
> Why don't you guys simply increment the third digit in the extended
> stable tree and get support for KERNEL_VERSION() for free? You always
> start after the respective stable branch has reached EOL, don't you?

Yes, we only start after the stable branch has reached EOL.

We don't increment the third integer for the extended-stable branches
(we add a fourth integer instead) in order to avoid the possibility of a
collision if Greg KH were to ever release a "special" post-EOL version
of one of his branches.

 -Kamal



  reply	other threads:[~2014-06-20 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 14:44 [PATCH] Makefile: version.h macros KERNEL_EXTRAVERSION, LINUX_EXTRAVERSION_CODE Kamal Mostafa
2014-06-20  9:39 ` Michal Marek
2014-06-20 15:47   ` Kamal Mostafa [this message]
2014-06-20 20:34     ` Michal Marek
2014-06-20 20:56       ` Greg KH

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=1403279278.14743.64.camel@fourier \
    --to=kamal@canonical.com \
    --cc=greg@kroah.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=mmarek@suse.cz \
    /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