Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] [V5] lttng-2.0 new recipe
Date: Sun, 15 Jan 2012 20:58:20 -0800	[thread overview]
Message-ID: <4F13AE6C.90607@linux.intel.com> (raw)
In-Reply-To: <cover.1326418292.git.zumeng.chen@windriver.com>

On 01/12/2012 05:44 PM, Zumeng Chen wrote:
> V5 Changes vs all previous versions:
> 1 ) fixed all Darren's comments;
> 2 ) fixed all Saul's comments;
>      +LICENSE = "MIT&  GPLv2" for 0004-babeltrace..
>      Upstream-Status: Pending for lttng-tools-fix-compiling..
>      +LICENSE = "GPLv2&  LGPLv2.1" for 0002-lttng-tools-..
>
> Thanks,
> Zumeng
>
> The following changes since commit 0f4d99d207b224bb9ce23de00a48f795ae20b3a0:
>
>    multilib.conf: Clean up file and add missing entries for various dependencies (2012-01-11 23:53:32 +0000)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib zumeng/lttng-2.0
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zumeng/lttng-2.0
>
> Zumeng Chen (4):
>    lttng-ust: Update to 2.0
>    lttng-tools: Update to 2.0-pre16
>    lttng-modules: Update to 2.0
>    babeltrace: Integrated from version 0.8
>
>   meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb    |   28 +++++++++++++
>   ...modules-replace-KERNELDIR-with-KERNEL_SRC.patch |   41 ++++++++++++++++++++
>   .../lttng-2.0/lttng-modules_2.0.pre11.bb           |   27 +++++++++++++
>   ...tools-fix-compiling-error-for-powerpc-arm.patch |   27 +++++++++++++
>   .../lttng-2.0/lttng-tools_2.0-pre16.bb             |   30 ++++++++++++++
>   meta/recipes-kernel/lttng-2.0/lttng-ust_1.9.4.bb   |   25 ++++++++++++
>   6 files changed, 178 insertions(+), 0 deletions(-)
>   create mode 100644 meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
>   create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch
>   create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-modules_2.0.pre11.bb
>   create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-tools-fix-compiling-error-for-powerpc-arm.patch

Zumeng,

My apologies for not catching this before, I just noticed that these 
patch files are not in a subdirectory, they should be located in a 
directory that is matches either the recipe name or recipe name with 
version (if they are specific to that version of the upstream).

Sau!

>   create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-tools_2.0-pre16.bb
>   create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-ust_1.9.4.bb
>



  parent reply	other threads:[~2012-01-16  5:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  1:44 [PATCH 0/4] [V5] lttng-2.0 new recipe Zumeng Chen
2012-01-13  1:44 ` [PATCH 1/4] lttng-ust: Update to 2.0 Zumeng Chen
2012-01-13  1:44 ` [PATCH 2/4] lttng-tools: Update to 2.0-pre16 Zumeng Chen
2012-01-13  1:44 ` [PATCH 3/4] lttng-modules: Update to 2.0 Zumeng Chen
2012-01-13  1:44 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-16  4:58 ` Saul Wold [this message]
2012-01-16  5:09   ` [PATCH 0/4] [V5] lttng-2.0 new recipe Zumeng Chen

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=4F13AE6C.90607@linux.intel.com \
    --to=sgw@linux.intel.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