From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
<mark.hatle@windriver.com>, <richard.purdie@linuxfoundation.org>
Subject: [PATCH V3 0/3] sstatesig: add support to dump incremental locked signatures
Date: Thu, 18 Sep 2014 15:23:40 +0800 [thread overview]
Message-ID: <cover.1411023982.git.hongxu.jia@windriver.com> (raw)
How to test incrementally locked signature dump:
1) Create a new build
2) Dump locked sig file for db
$ bitbake -S none db
...
Writing locked sigs to /home/jiahongxu/yocto/build-20140904-yocto/locked-sigs.inc
NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and all succeeded.
...
3) Back up locked-sigs.inc
$ cp locked-sigs.inc locked-sigs.inc.bak
4) Dump locked sig file for db again
$ bitbake -S none db
...
Writing locked sigs to /home/jiahongxu/yocto/build-20140904-yocto/locked-sigs.inc
NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and all succeeded.
...
5) Compare locked-sigs.inc and locked-sigs.inc.bak to verify nothing changed
$ vimdiff locked-sigs.inc locked-sigs.inc.bak
6) Require locked-sigs.inc
vim local.conf
...
require "${TOPDIR}/locked-sigs.inc"
...
7) Incrementally dump locked sig file for world
$ bitbake -S none world
...
Writing locked sigs to /home/jiahongxu/yocto/build-20140904-yocto/locked-sigs.inc
NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and all succeeded.
...
8) Compare locked-sigs.inc and locked-sigs.inc.bak to verify incrementally dumping
$ vimdiff locked-sigs.inc locked-sigs.inc.bak
9) Back up locked-sigs.inc
$ cp locked-sigs.inc locked-sigs.inc.bak
10) Dump for world again
$ bitbake -S none world
...
Writing locked sigs to /home/jiahongxu/yocto/build-20140904-yocto/locked-sigs.inc
Nothing added to /home/jiahongxu/yocto/build-20140904-yocto/locked-sigs.inc
NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and all succeeded.
...
11) Compare locked-sigs.inc and locked-sigs.inc.bak to verify nothing changed
$ vimdiff locked-sigs.inc locked-sigs.inc.bak
//Hongxu
The following changes since commit 280b6d0011f101e7a8edabd34c265b37a2f791ed:
sstatesig: fix overrides behaviour to remove SIGGEN_LOCKEDSIGS_i586 (2014-09-17 22:00:26 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/locked-sstate
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/locked-sstate
Hongxu Jia (3):
sstatesig: Only dump incremental locked signatures
sstatesig: add new item checking for locked signature dump
sstatesig: fix to support unincremental locked signature dump
meta/lib/oe/sstatesig.py | 33 ++++++++++++++++++++++++++++-----
1 file changed, 28 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2014-09-18 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 7:23 Hongxu Jia [this message]
2014-09-18 7:23 ` [PATCH 1/3] sstatesig: Only dump incremental locked signatures Hongxu Jia
2014-09-18 13:47 ` Richard Purdie
2014-09-18 13:56 ` Mark Hatle
2014-09-18 15:10 ` Hongxu Jia
2014-09-18 16:47 ` Hongxu Jia
2014-09-18 7:23 ` [PATCH 2/3] sstatesig: add new item checking for locked signature dump Hongxu Jia
2014-09-18 7:23 ` [PATCH 3/3] sstatesig: fix to support unincremental " Hongxu Jia
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.1411023982.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=mark.hatle@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 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.