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
Subject: [PATCH 0/2] kernel: consolidated pull request
Date: Tue, 4 Feb 2014 12:34:24 -0500	[thread overview]
Message-ID: <cover.1391534980.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

Consolidated is a bit of a strong word here, since there are
only two patches .. but I'd rather send them as a series of
my pending changes versus two separate pulls.

Once is an update of the 3.10 tree to include the 3.10 LTSI
content, this gets us new BSP support and a few features. The
merge was smooth, but I did build and boot all qemu boards to
be sure.

The second change is a tweak I made to speed up the kernel
installation phase. It's a simple change that saves nearly a 
minute on my local tests. As the patch states, I kept things
simple instead of getting really arcane with find and mixing
multiple options (it is already getting unreadible, and I
didn't want to make it worse).

From the patch:

    Time for install before this change:

     real    2m48.563s
     user    0m35.220s
     sys     0m33.036s

    Time for install after this change:

     real    1m21.301s
     user    0m33.160s
     sys     0m28.388s

I've been running with the install change for quite some time
now, and haven't seen any breakage.

Bruce

The following changes since commit 82f9c2bcff3e977beefde6048d2ba32d17acbbd0:

  wic: Hook up --debug option (2014-02-04 12:57:36 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (2):
  kernel: stop using -exec rm for deleting files
  linux-yocto/3.10: integrate LTSI

 meta/classes/kernel.bbclass                        | 18 +++++++++++++++---
 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_3.10.bb      | 14 +++++++-------
 4 files changed, 25 insertions(+), 13 deletions(-)

-- 
1.8.1.2



             reply	other threads:[~2014-02-04 17:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 17:34 Bruce Ashfield [this message]
2014-02-04 17:34 ` [PATCH 1/2] kernel: stop using -exec rm for deleting files Bruce Ashfield
2014-02-04 23:26   ` Richard Purdie
2014-02-05  0:35     ` Bruce Ashfield
2014-02-05  1:36       ` Paul Barker
2014-02-05  3:10         ` Bruce Ashfield
2014-02-09 12:06   ` Richard Purdie
2014-02-09 14:36     ` Bruce Ashfield
2014-02-10 13:32     ` Bruce Ashfield
2014-02-10 17:17     ` Bruce Ashfield
2014-02-10 17:23       ` Richard Purdie
2014-02-04 17:34 ` [PATCH 2/2] linux-yocto/3.10: integrate LTSI Bruce Ashfield
2014-02-07 16:42   ` Saul Wold
2014-02-07 16:44     ` Bruce Ashfield
2014-02-07 16:46       ` Darren Hart
2014-02-07 16:47         ` Darren Hart
2014-02-07 16:48           ` Bruce Ashfield
2014-02-07 16:55             ` Darren Hart
2014-02-07 16:57               ` Bruce Ashfield
2014-02-07 17:24               ` Bruce Ashfield
2014-02-07 17:32                 ` Darren Hart
2014-02-07 19:22     ` Bruce Ashfield

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