All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Anand Balagopalakrishnan <anandb@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [[thud] PATCH 1/1] linux-ti-staging: update to latest version
Date: Wed, 19 Jun 2019 14:20:41 -0400	[thread overview]
Message-ID: <20190619182041.GG32001@beryl> (raw)
In-Reply-To: <1560960696-17318-1-git-send-email-anandb@ti.com>

On Wed, Jun 19, 2019 at 09:41:36PM +0530, Anand Balagopalakrishnan wrote:
> Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
> ---
>  recipes-kernel/linux/linux-ti-staging_4.19.bb | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-ti-staging_4.19.bb b/recipes-kernel/linux/linux-ti-staging_4.19.bb
> index 26b388b..ceec516 100644
> --- a/recipes-kernel/linux/linux-ti-staging_4.19.bb
> +++ b/recipes-kernel/linux/linux-ti-staging_4.19.bb
> @@ -56,11 +56,11 @@ S = "${WORKDIR}/git"
>  
>  BRANCH = "ti-linux-4.19.y"
>  
> -SRCREV = "7d94bf0b5ba7a68aa735c422f40d53957d094f8b"
> -PV = "4.19.38+git${SRCPV}"
> +SRCREV = "d343b32d0ab8262cf0a0fa8f4bd2bf1745685984"
> +PV = "4.19.50+git${SRCPV}"
>  
>  # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
> -MACHINE_KERNEL_PR_append = "c"
> +MACHINE_KERNEL_PR_append = "d"

PR should be reset when PV gets updated.

Also, corresponding RT srecipe hould be updated as well.


>  PR = "${MACHINE_KERNEL_PR}"
>  
>  KERNEL_GIT_URI = "git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git"
> -- 
> 1.9.1
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2019-06-19 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 16:11 [[thud] PATCH 1/1] linux-ti-staging: update to latest version Anand Balagopalakrishnan
2019-06-19 18:20 ` Denys Dmytriyenko [this message]
2019-06-19 18:21   ` Denys Dmytriyenko
2019-06-20  9:15     ` Anand Balagopalakrishnan

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=20190619182041.GG32001@beryl \
    --to=denys@ti.com \
    --cc=anandb@ti.com \
    --cc=meta-arago@arago-project.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.