Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Chong.Lu@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/3] lttng-ust: update commit to fix compiling issues
Date: Thu, 05 Dec 2013 11:11:22 -0800	[thread overview]
Message-ID: <52A0CFDA.1060906@linux.intel.com> (raw)
In-Reply-To: <1386224059-29263-1-git-send-email-Chong.Lu@windriver.com>

On 12/04/2013 10:14 PM, Chong.Lu@windriver.com wrote:
> From: Chong Lu <Chong.Lu@windriver.com>
>
> Update commit in order to add patches like below:
>
> 	doc/examples: error out when a subdir make fails
> 	fix: lttng-gen-tp: add missing spaces around flags
>
> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
> ---
>   meta/recipes-kernel/lttng/lttng-ust_2.3.0.bb |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/lttng/lttng-ust_2.3.0.bb b/meta/recipes-kernel/lttng/lttng-ust_2.3.0.bb
> index fed572a..f3a6b05 100644
> --- a/meta/recipes-kernel/lttng/lttng-ust_2.3.0.bb
> +++ b/meta/recipes-kernel/lttng/lttng-ust_2.3.0.bb
> @@ -18,7 +18,7 @@ RPROVIDES_${PN} = "lttng2-ust"
>   RREPLACES_${PN} = "lttng2-ust"
>   RCONFLICTS_${PN} = "lttng2-ust"
>
> -SRCREV = "9f00ce32b103eed13524c876757b6611c5922382"
> +SRCREV = "e6a8d841217f651e86c8e133e0edbbb667c11055"
>   PV = "2.3.0"
>   PE = "2"
>
>
lttng-ust was updated to 2.3.1, can you update your patches accordingly 
please.

Thanks
	Sau!



      parent reply	other threads:[~2013-12-05 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  6:14 [PATCH V2 1/3] lttng-ust: update commit to fix compiling issues Chong.Lu
2013-12-05  6:14 ` [PATCH V2 2/3] lttng-ust: Using toolchain to compile examples Chong.Lu
2013-12-05  6:14 ` [PATCH V2 3/3] lttng-ust: fix python interpret path Chong.Lu
2013-12-05 19:11 ` Saul Wold [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=52A0CFDA.1060906@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Chong.Lu@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