All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders.darander@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 3/5] linux-kernel-base: add support for Linux 3.x
Date: Tue, 21 Jun 2011 21:10:20 +0200	[thread overview]
Message-ID: <BANLkTinkNcN8RBcZapj5xF=q_p4O++trgg@mail.gmail.com> (raw)
In-Reply-To: <1308681938.3083.11.camel@lenovo.internal.reciva.com>

On Tue, Jun 21, 2011 at 20:45, Phil Blundell <pb@pbcl.net> wrote:
> On Tue, 2011-06-21 at 20:18 +0200, Anders Darander wrote:
>> Return 2.X as major version for kernels 2.X, and return
>> X for kernels X.Y (X>=3).
>
> I'm not quite sure I understand what this particular logic is useful
> for.  If we're removing 2.4 support (which I'm fairly relaxed about)
> then it seems as though this whole "kernel_majorversion" thing can and
> should just go away.

If we should remove the kernel_majorversion, we'll have to double check that
this isn't used somewhere else. If it isn't, I'm all in favor of removing it.

> Or, alternatively, perhaps it should be mapped into a more abstract kind
> of "kernel epoch" thing which treats 2.6 and 3.0 as basically the same.

If we keep the kernel_majorversion, we'll need to have something
similar to this,
as the major version up to 2.6 was determined by X.Y. From 3.0, only the first
digit represents the major number; while the second digit (0 in 3.0)
is equal to
x in 2.6.x. Thus, the function to determine the major version has to
return either
2.6 or 3.

Regards,
Anders



  reply	other threads:[~2011-06-21 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 18:18 [RFC PATCH 0/5] Linux 3.0 build support Anders Darander
2011-06-21 18:18 ` [RFC PATCH 1/5] Remove support for building 2.4 kernels Anders Darander
2011-06-21 18:47   ` Phil Blundell
2011-06-21 19:05     ` Anders Darander
2011-06-21 18:18 ` [RFC PATCH 2/5] module-init-tools-cross: add provides for depmod-3 Anders Darander
2011-06-21 18:22   ` Koen Kooi
2011-06-21 18:40     ` Anders Darander
2011-06-21 18:46   ` Phil Blundell
2011-06-21 19:03     ` Anders Darander
2011-06-22  5:49       ` Anders Darander
2011-06-21 18:18 ` [RFC PATCH 3/5] linux-kernel-base: add support for Linux 3.x Anders Darander
2011-06-21 18:45   ` Phil Blundell
2011-06-21 19:10     ` Anders Darander [this message]
2011-06-22 10:22       ` Phil Blundell
2011-06-22 10:41         ` Anders Darander
2011-06-21 18:18 ` [RFC PATCH 4/5] modutils-initscripts: move recipe prior to modutils removal Anders Darander
2011-06-21 18:18 ` [RFC PATCH 5/5] modutils: remove modutils Anders Darander

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='BANLkTinkNcN8RBcZapj5xF=q_p4O++trgg@mail.gmail.com' \
    --to=anders.darander@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.