Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Yuan Chao <yuanc.fnst@cn.fujitsu.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] [PATCH] kpatch: upgrade 0.7.1 -> 0.8.0
Date: Fri, 23 Aug 2019 11:36:38 +0300	[thread overview]
Message-ID: <20190823083638.GB9224@localhost> (raw)
In-Reply-To: <20190823052215.3208-1-yuanc.fnst@cn.fujitsu.com>

On Fri, Aug 23, 2019 at 02:22:15PM +0900, Yuan Chao wrote:
> Signed-off-by: Yuan Chao <yuanc.fnst@cn.fujitsu.com>
> ---
>  meta-oe/recipes-kernel/kpatch/kpatch_git.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-oe/recipes-kernel/kpatch/kpatch_git.bb b/meta-oe/recipes-kernel/kpatch/kpatch_git.bb
> index dc247942f..508bddb86 100644
> --- a/meta-oe/recipes-kernel/kpatch/kpatch_git.bb
> +++ b/meta-oe/recipes-kernel/kpatch/kpatch_git.bb
> @@ -2,9 +2,9 @@ require kpatch.inc
>  
>  LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
> -SRCREV = "d7c5810e2a6acacfa5fec1e38d2f75af8e8c818c"
> +SRCREV = "2a29bc7dea9a7da12705c7b50315eee1acdd9156"
>  
> -PV = "0.7.1+git${SRCPV}"
> +PV = "0.8.0+git${SRCPV}"
>...

This is exactly the 0.8.0 release, please set
  PV = "0.8.0"

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-08-23  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23  5:22 [meta-oe] [PATCH] kpatch: upgrade 0.7.1 -> 0.8.0 Yuan Chao
2019-08-23  8:36 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-23  5:28 Zang Ruochen

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=20190823083638.GB9224@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=yuanc.fnst@cn.fujitsu.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