From: Darren Hart <dvhart@linux.intel.com>
To: Zumeng Chen <zumeng.chen@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 4/4] babeltrace: Integrated from version 0.8
Date: Sat, 07 Jan 2012 07:54:06 -0800 [thread overview]
Message-ID: <4F086A9E.3080306@linux.intel.com> (raw)
In-Reply-To: <6d11d61757dd2d5f41496f929f46653e25b2870e.1325824274.git.zumeng.chen@windriver.com>
On 01/05/2012 10:11 PM, Zumeng Chen wrote:
> It provides trace read and write libraries, as well as a trace converter.
>
> Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
> ---
> meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb | 30 +++++++++++++++++++++++
> 1 files changed, 30 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
>
> diff --git a/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb b/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
> new file mode 100644
> index 0000000..86a9d01
> --- /dev/null
> +++ b/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
> @@ -0,0 +1,30 @@
> +SUMMARY = "Babeltrace - Trace Format Babel Tower"
> +DESCRIPTION = "Babeltrace provides trace read and write libraries in host side,\
> + as well as a trace converter, which used to convert LTTng 2.0 \
> + traces into human-readable log."
In the previous patches you aligned the additional lines with column 0,
here you indent with tabs and spaces. A quick survey of the existing
sources suggest the DESCRIPTION field typically does not indent the
subsequent lines.
> +HOMEPAGE = "http://www.efficios.com/babeltrace/"
> +BUGTRACKER = "n/a"
> +
> +LICENSE = "MIT & GPLV2"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=8d1a03b3c17bdd158b3cbb34813b1423"
> +
> +inherit autotools
> +
> +DEPENDS = "gtk+ util-linux"
> +
> +SRCREV = "31e670293588d7882a232bc14b93d5e956fa43f4"
> +PV = "0.8+git${SRCPV}"
> +PR = "r0"
> +
> +SRC_URI += "git://git.efficios.com/babeltrace.git;protocol=git"
> +
This should be a "=" assignment, not "+=".
> +S = "${WORKDIR}/git"
> +
> +do_configure_prepend () {
> + ${S}/bootstrap
Please use tabs for indentation here.
> +}
> +
> +# Due to liburcu not building on MIPS currently this recipe needs to
> +# be limited also.
> +# So here let us first suppport x86/arm/powerpc platforms now.
> +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|powerpc.*)-linux'
Again, I think you want to filter based on target arch.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-01-07 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 6:11 [PATCH 0/4]lttng-2.0 new recipe Zumeng Chen
2012-01-06 6:11 ` [PATCH 1/4] lttng-ust: Integrate into yocto linux Zumeng Chen
2012-01-07 2:01 ` Darren Hart
2012-01-09 4:27 ` Zumeng Chen
2012-01-06 6:11 ` [PATCH 2/4] lttng-tools: Integrated from git repo Zumeng Chen
2012-01-06 6:27 ` Zumeng Chen
2012-01-07 2:05 ` Darren Hart
2012-01-09 4:31 ` Zumeng Chen
2012-01-06 6:11 ` [PATCH 3/4] lttng-modules: from lttng-modules 2.0 " Zumeng Chen
2012-01-07 2:10 ` Darren Hart
2012-01-09 4:33 ` Zumeng Chen
2012-01-06 6:11 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-07 15:54 ` Darren Hart [this message]
2012-01-09 4:35 ` Zumeng Chen
[not found] <cover.1326099771.git.zumeng.chen@windriver.com>
2012-01-09 9:24 ` Zumeng Chen
[not found] <cover.1326210673.git.zumeng.chen@windriver.com>
2012-01-10 16:11 ` Zumeng Chen
[not found] <cover.1326244852.git.zumeng.chen@windriver.com>
2012-01-11 1:31 ` Zumeng Chen
-- strict thread matches above, loose matches on Subject: below --
2012-01-12 3:10 [V4] [PATCH 0/4] lttng-2.0 new recipe for merge Zumeng Chen
2012-01-12 3:11 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-12 22:06 ` Saul Wold
2012-01-13 0:57 ` zumeng.chen
2012-01-13 1:44 [PATCH 0/4] [V5] lttng-2.0 new recipe Zumeng Chen
2012-01-13 1:44 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-16 16:06 [PATCH 0/4] [V6] lttng-2.0 new recipe Zumeng Chen
2012-01-16 16:06 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 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=4F086A9E.3080306@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.org \
--cc=zumeng.chen@windriver.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.