kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Main Linux kernel vs Ubuntu kernel
Date: Sat, 9 Jun 2018 15:57:11 +0200	[thread overview]
Message-ID: <20180609135711.GA28065@kroah.com> (raw)
In-Reply-To: <CAPY=qRT993xC9PGnwqk6wWgLJ7yUMaoFQPvhxUrCtLXz4TJnPA@mail.gmail.com>

On Sat, Jun 09, 2018 at 05:17:45PM +0530, Subhashini Rao Beerisetty wrote:
> My question related to backward compatibility is: If an API?s signature
> changed from kernel version x.y.z onwards, does the mainline tree code uses
> the below mentioned logic?
> 
> 
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(x,y,z)
> 
> #else
> 
> #endif

No, mainline kernel code does not have #ifdefs at all, it is not needed.

Remember, all drivers are included in the kernel release at once, so
there is no need for such checks as they all work for the kernel they
are contained in.

> Regarding long term release kernels, what here ?long term? means?

Did you read this:
	https://www.kernel.org/category/releases.html

It should explain all of this.

> For e.g.  v4.4 is part of long term release kernel released in
> 2016-01-10 and it?s projected EOL is Feb, 2022, here what?s the
> meaning of EOL?

End Of Life.

> How to backport the bug fixes for older kernel tree (for e.g. v4.4) and
> what is the selection criteria for choosing which bug fixes should go for
> backporting?

Did you read this:
	https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

Also, please read the kernel development process documentation, it
should have answered these questions for you and will cover lots of this
type of thing.

thanks,

greg k-h

  reply	other threads:[~2018-06-09 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 18:32 Main Linux kernel vs Ubuntu kernel Subhashini Rao Beerisetty
2018-06-08 19:27 ` Shyam Saini
2018-06-08 21:07   ` valdis.kletnieks at vt.edu
2018-06-09 11:47     ` Subhashini Rao Beerisetty
2018-06-09 13:57       ` Greg KH [this message]
2018-06-11  2:29       ` valdis.kletnieks at vt.edu

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=20180609135711.GA28065@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).