Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto: sync meta and LINUX_VERSION
Date: Thu, 25 Aug 2011 00:36:33 -0400	[thread overview]
Message-ID: <cover.1314246387.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

When doing some clean build testing on my latest changes (given that
I'm a bit paranoid), I noticed the kernel config audit throwing some
warnings (unset values, etc).

The root cause is that when the config fragments are processed they
are assembled into a file with the version string from the kernel 
tree (which was at v3.0) while the recipe tells the audit to check
against 3.0.x. Which means nothing is checked.

The fix is simple, I've bumped the internal version to 3.0.3 and 
pushed it out. The audits are now clean.

.. and this time, I'm nearly sure I pushed these to the proper branch
and generated a pull against it.

The following changes since commit 9ca6806de9d9df9d901774c1b23a14f28f10a844:

  docuementation/poky-ref-manual/ref-structure.xml: Changed SRCDATE reference (2011-08-24 19:59:55 -0700)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel-oe
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe

Bruce Ashfield (1):
  linux-yocto: update meta SRCREV to sync version strings

 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.0.bb    |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
1.7.4.1




             reply	other threads:[~2011-08-25  4:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  4:36 Bruce Ashfield [this message]
2011-08-25  4:36 ` [PATCH 1/1] linux-yocto: update meta SRCREV to sync version strings Bruce Ashfield
2011-08-25 15:01   ` Richard Purdie
2011-08-25  7:28 ` does it support mercurial? Ni Qingliang
2011-08-25 15:00   ` Richard Purdie

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=cover.1314246387.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.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