From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] libz160: Add compatible machine to 'mx5'
Date: Wed, 30 Apr 2014 13:31:20 +0000 [thread overview]
Message-ID: <87k3a7gd07.fsf@parenteses.org> (raw)
In-Reply-To: <1398863625-2525-1-git-send-email-otavio@ossystems.com.br> (Otavio Salvador's message of "Wed, 30 Apr 2014 10:13:45 -0300")
On Wed, 30 Apr 2014 10:13:45 -0300 Otavio Salvador <otavio@ossystems.com.br> wrote:
> Restrict the recipe to be used for 'mx5' SoCs only.
With regard to the patch summary: isn't it the other way around? I
mean, something like "add mx5 to compatible machine".
> Change-Id: I9084cc525c7136b23e1c5522079c38bd12df7087
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> recipes-graphics/amd-gpu-x11-bin/libz160_11.09.01.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-graphics/amd-gpu-x11-bin/libz160_11.09.01.bb b/recipes-graphics/amd-gpu-x11-bin/libz160_11.09.01.bb
> index 16cfa9f..1ff762a 100644
> --- a/recipes-graphics/amd-gpu-x11-bin/libz160_11.09.01.bb
> +++ b/recipes-graphics/amd-gpu-x11-bin/libz160_11.09.01.bb
> @@ -29,3 +29,5 @@ INSANE_SKIP_${PN} = "ldflags"
> INSANE_SKIP_${PN}-dev = "ldflags"
> FILES_${PN} = "${libdir}/*.so"
> FILES_${PN}-dev = "${includedir}"
> +
> +COMPATIBLE_MACHINE = "(mx5)"
> --
> 2.0.0.rc0
Best wishes.
Mario
--
http://www.ossystems.com.br
next prev parent reply other threads:[~2014-04-30 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 13:13 [meta-fsl-arm][PATCH] libz160: Add compatible machine to 'mx5' Otavio Salvador
2014-04-30 13:31 ` Mario Domenech Goulart [this message]
2014-04-30 13:35 ` Otavio Salvador
2014-04-30 13:50 ` Mario Domenech Goulart
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=87k3a7gd07.fsf@parenteses.org \
--to=mario@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.