Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] kern-tools: fix multi-layer patch application
Date: Tue, 29 Sep 2015 10:07:03 -0700	[thread overview]
Message-ID: <CBC9858A-0875-463A-A0C0-0C34EEF752F0@gmail.com> (raw)
In-Reply-To: <6b281d94cd5d112840fc39b017be201a41e65658.1443536748.git.bruce.ashfield@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]


> On Sep 29, 2015, at 7:31 AM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
> 
> 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>
> ---
> meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index 27df02ab7a44..18be4ad61598 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
> 
> DEPENDS = "git-native"
> 
> -SRCREV = "b7642a7c3f685850ffbb961313e6a593adb05370"
> +SRCREV = “1fb91c2965193df894089fbcbcafe3bf775c21fd"

this works well now.

> PR = "r12"
> PV = "0.2+git${SRCPV}"
> 
> --
> 2.1.0
> 
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

      reply	other threads:[~2015-09-29 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 14:31 [PATCH 0/4] linux-yocto: consolidated pull request Bruce Ashfield
2015-09-29 14:31 ` [PATCH 1/4] linux-yocto-rt/4.1: integrate axxia BSP Bruce Ashfield
2015-09-29 14:31 ` [PATCH 2/4] linux-yocto/4.1: update to 4.1.8 -stable Bruce Ashfield
2015-09-29 14:31 ` [PATCH 3/4] linux-yocto/4.1: braswell bug fixes Bruce Ashfield
2015-09-29 14:31 ` [PATCH 4/4] kern-tools: fix multi-layer patch application Bruce Ashfield
2015-09-29 17:07   ` Khem Raj [this message]

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=CBC9858A-0875-463A-A0C0-0C34EEF752F0@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.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