All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denys@ti.com>
To: <s-anna@ti.com>
Cc: Khem Raj <raj.khem@gmail.com>, <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] [PATCH 2/2] ti-rpmsg-char: Mark these recipes to be TI SOC specific
Date: Mon, 26 Oct 2020 22:41:59 -0400	[thread overview]
Message-ID: <20201027024159.GP19741@beryl> (raw)
In-Reply-To: <03f490f1-ff1a-b3fc-6511-00b8d707eb6e@ti.com>

On Mon, Oct 26, 2020 at 09:19:29PM -0500, Suman Anna via lists.yoctoproject.org wrote:
> Hi Raj,
> 
> On 10/25/20 1:59 AM, Khem Raj wrote:
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> >  recipes-ti/ipc/ti-rpmsg-char.inc | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/recipes-ti/ipc/ti-rpmsg-char.inc b/recipes-ti/ipc/ti-rpmsg-char.inc
> > index b41e68eb..d08031cb 100644
> > --- a/recipes-ti/ipc/ti-rpmsg-char.inc
> > +++ b/recipes-ti/ipc/ti-rpmsg-char.inc
> > @@ -13,3 +13,6 @@ SRCREV = "9be402c2bf4053900b6b9a8092fbb42e7e303108"
> >  PV = "0.1.0+git${SRCPV}"
> >  
> >  S = "${WORKDIR}/git"
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > 
> 
> This looks ok, but I am trying to understand why this is needed in general (am
> still getting familiar with OE). Aren't the recipes processed only on
> packagegroups that include them?

Suman,

Some people like Khem do world builds - kind of like building kernel with 
"allyesconfig" to see any conflicts or incompatibilities...

-- 
Denys

  parent reply	other threads:[~2020-10-27  2:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25  6:59 [PATCH 1/2] ti-rpmsg-char-examples: Fix cross compile Khem Raj
2020-10-25  6:59 ` [PATCH 2/2] ti-rpmsg-char: Mark these recipes to be TI SOC specific Khem Raj
2020-10-27  2:19   ` [meta-ti] " Suman Anna
2020-10-27  2:30     ` Khem Raj
2020-10-27  2:45       ` Suman Anna
     [not found]       ` <1641B95DDCF93CD1.11545@lists.yoctoproject.org>
2020-10-29 21:53         ` Suman Anna
2020-10-27  2:41     ` Denys Dmytriyenko [this message]
2020-10-26 21:20 ` [meta-ti] [PATCH 1/2] ti-rpmsg-char-examples: Fix cross compile Denys Dmytriyenko
2020-10-26 23:24   ` Khem Raj
2020-10-27  2:43     ` Denys Dmytriyenko
     [not found]     ` <1641B93D38E82508.16876@lists.yoctoproject.org>
2020-10-29 18:09       ` Denys Dmytriyenko
2020-10-29 20:09         ` Khem Raj
2020-10-29 21:50           ` Suman Anna
2020-10-29 21:56             ` Denys Dmytriyenko

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=20201027024159.GP19741@beryl \
    --to=denys@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=raj.khem@gmail.com \
    --cc=s-anna@ti.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.