From: Denys Dmytriyenko <denys@ti.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH 2/4] jailhouse: Limit OE architectures to supported ones
Date: Mon, 15 Jul 2019 15:52:24 -0400 [thread overview]
Message-ID: <20190715195224.GG9038@beryl> (raw)
In-Reply-To: <20190713004324.12695-2-raj.khem@gmail.com>
On Fri, Jul 12, 2019 at 05:43:22PM -0700, Khem Raj wrote:
> Fixes
> ERROR: cannot map 'mips' to a jailhouse supported architecture
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> recipes-kernel/jailhouse/jailhouse-arch.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/recipes-kernel/jailhouse/jailhouse-arch.inc b/recipes-kernel/jailhouse/jailhouse-arch.inc
> index e06ec231..0546fa26 100644
> --- a/recipes-kernel/jailhouse/jailhouse-arch.inc
> +++ b/recipes-kernel/jailhouse/jailhouse-arch.inc
> @@ -18,3 +18,6 @@ def map_jh_arch(a, d):
> bb.error("cannot map '%s' to a jailhouse supported architecture" % a)
>
> export JH_ARCH = "${@map_jh_arch(d.getVar('TARGET_ARCH', True), d)}"
> +
> +COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
> +
Applying: jailhouse: Limit OE architectures to supported ones
.git/rebase-apply/patch:15: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
I'll fix it myself.
> --
> 2.22.0
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2019-07-15 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 0:43 [PATCH 1/4] ti-display-sharing-fw: Do not strip during staging sysroot stage Khem Raj
2019-07-13 0:43 ` [PATCH 2/4] jailhouse: Limit OE architectures to supported ones Khem Raj
2019-07-15 19:52 ` Denys Dmytriyenko [this message]
2019-07-13 0:43 ` [PATCH 3/4] jailhouse: Replace tabs with spaces in python code Khem Raj
2019-07-15 20:12 ` Denys Dmytriyenko
2019-07-17 1:27 ` Khem Raj
2019-07-13 0:43 ` [PATCH 4/4] jailhouse: Pin to TI SOCs Khem Raj
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=20190715195224.GG9038@beryl \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=raj.khem@gmail.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.