All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] linux-keystone: Update latest tag
Date: Sat, 22 Feb 2014 23:50:44 -0500	[thread overview]
Message-ID: <20140223045044.GX22890@denix.org> (raw)
In-Reply-To: <1393129856-9624-1-git-send-email-sam.nelson@ti.com>

On Sat, Feb 22, 2014 at 11:30:56PM -0500, Sam Nelson wrote:
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> 
> ---
> Not sure whether need a PR bump

Yes, this one usually needs. Well, your SRCREV went up in both cases, so will 
still work w/o a PR bump, but it's still a good idea to bump PR when updating 
SRCREV only and PV stays the same. Kernel recipes have MACHINE_KERNEL_PR_append 
for that.

-- 
Denys


> ---
> ---
>  recipes-kernel/linux/linux-keystone-rt_3.10.bb |    4 ++--
>  recipes-kernel/linux/linux-keystone_3.10.bb    |    4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-keystone-rt_3.10.bb b/recipes-kernel/linux/linux-keystone-rt_3.10.bb
> index 9c2f904..3965dfa 100644
> --- a/recipes-kernel/linux/linux-keystone-rt_3.10.bb
> +++ b/recipes-kernel/linux/linux-keystone-rt_3.10.bb
> @@ -17,8 +17,8 @@ KERNEL_DEVICETREE_keystone-evm = "k2hk-evm.dtb"
>  
>  KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
>  
> -#This commit corresponds to "K2_RT_LINUX_03.10.10_13.12"
> -SRCREV = "8fa9091d0f9c91a048a975ddebbf2f492e73bf61"
> +#This commit corresponds to "K2_RT_LINUX_03.10.10_14.02"
> +SRCREV = "c78aa253ac385faae8b6c845a388e215395a8010"
>  PV = "3.10.10"
>  
>  BRANCH = "master-rt"
> diff --git a/recipes-kernel/linux/linux-keystone_3.10.bb b/recipes-kernel/linux/linux-keystone_3.10.bb
> index 2384ede..f063c0c 100644
> --- a/recipes-kernel/linux/linux-keystone_3.10.bb
> +++ b/recipes-kernel/linux/linux-keystone_3.10.bb
> @@ -17,8 +17,8 @@ KERNEL_DEVICETREE_keystone-evm = "k2hk-evm.dtb"
>  
>  KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
>  
> -#This commit corresponds to "K2_LINUX_03.10.10_13.12"
> -SRCREV = "335d14b1c2ce23585835243126c6acba89067ecf"
> +#This commit corresponds to "K2_LINUX_03.10.10_14.02"
> +SRCREV = "93515476b357304e6fc075c004a1cfa91a0751d0"
>  PV = "3.10.10"
>  
>  BRANCH = "master"
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
> 


  reply	other threads:[~2014-02-23  4:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  4:30 [PATCH] linux-keystone: Update latest tag Sam Nelson
2014-02-23  4:50 ` Denys Dmytriyenko [this message]
2014-02-23 13:47   ` Nelson, Sam
2014-02-24 16:01     ` Maupin, Chase
2014-02-24 17:41     ` Denys Dmytriyenko

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=20140223045044.GX22890@denix.org \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sam.nelson@ti.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 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.