diff options
| author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-09-29 10:31:35 -0400 | 
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-10-01 07:40:23 +0100 | 
| commit | 692f1333e257556e7462b2436dd60e865869349c (patch) | |
| tree | 9e1cfeb624b9f7766985ecdcffd534d81ffe7f52 /scripts/lib/wic/kickstart/custom_commands | |
| parent | 2ea7533b5d45bb459284dd1c3f81d4bcac88f882 (diff) | |
| download | openembedded-core-692f1333e257556e7462b2436dd60e865869349c.tar.gz openembedded-core-692f1333e257556e7462b2436dd60e865869349c.tar.bz2 openembedded-core-692f1333e257556e7462b2436dd60e865869349c.zip | |
kern-tools: fix multi-layer patch application
Updating the kern-tools SRCREV to import the following fix:
    kgit-meta: resume after last applied patch
    When the auto-resume (resume point detection) was removed from the
    processing of a meta-series, it ignored the fact that a single patch
    series may in fact be processed a number of times.
    Two layers patching a kernel will generate two different runs on the
    same branch, which always start at patch one. This will obviously
    break with duplicate patches.
    To avoid this, we simply track the last patch applied, and
    explicitly
    tell the patch scripts where to start. This gets us resume
    functionality, without the overhead of resume point detection.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/wic/kickstart/custom_commands')
0 files changed, 0 insertions, 0 deletions
