All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>, Diego <diego.ml@zoho.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Kernel Image name
Date: Wed, 26 Mar 2014 07:17:41 -0700	[thread overview]
Message-ID: <5332E185.5050604@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKqV-XvPyeHGU8f9jiNfZDLe_1ksk+3meBn8xG23u6kCOg@mail.gmail.com>

Hi Otavio and Diego,

On 03/26/2014 05:40 AM, Otavio Salvador wrote:
> On Wed, Mar 26, 2014 at 8:54 AM, Diego <diego.ml@zoho.com> wrote:
>> Hi everybody,
>>
>> is anybody else getting working but oddly named kernel images with repeated
>> "3.10.17"?
>>
>> In particulare i'm seeing:
>> $ mkimage -l uImage
>> Image Name:   Linux-3.10.173.10.17_beta+yocto+
>>
>> and modules named:
>> "/lib/modules/3.10.173.10.17_beta+yocto+g..."
>>
>> I'm using Boundary Nitrogen6x.
>
> I didn't test it recently but Eric does quite often. Eric, did you see it?
>

I hadn't noticed it, but I see where it's coming from:

The LOCALVERSION tag here:
	http://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary_3.10.17.bb#L12

Looks like it should start with a separator, and not contain
the kernel version:
	http://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary_3.0.35.bb#L12

I think the proper value for that variable is this:

	LOCALVERSION = "-1.0.0_beta+yocto"

I'll send a patch shortly.

Regards,


Eric


  reply	other threads:[~2014-03-26 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 11:54 Kernel Image name Diego
2014-03-26 12:40 ` Otavio Salvador
2014-03-26 14:17   ` Eric Nelson [this message]
2014-03-26 14:38   ` [PATCH] linux-boundary: remove redundant version tag from 3.10.17 kernel Eric Nelson
2014-03-26 14:40     ` Eric Nelson
2014-03-26 14:44   ` [meta-fsl-arm-extra][PATCH] linux-boundary: remove version number " Eric Nelson
2014-03-26 15:01     ` Otavio Salvador
2014-03-26 15:08       ` Eric Nelson

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=5332E185.5050604@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=diego.ml@zoho.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.