From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>,
Darren Etheridge <detheridge@ti.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm
Date: Tue, 29 Mar 2022 00:49:33 -0400 [thread overview]
Message-ID: <20220329044933.GN23554@denix.org> (raw)
In-Reply-To: <20220325184151.16940-1-afd@ti.com>
On Fri, Mar 25, 2022 at 01:41:48PM -0500, Andrew F. Davis via lists.yoctoproject.org wrote:
> In many places we use "j7" the family when we should be using a
> specific SoC or EVM and vice-versa. For instance when including
> graphics drivers we add for all "j7" family, but what we really
> want is only for some specific j7 SoC.
>
> First step in untangling this is to make it clear that there is
> no SoC called j7. There is a SoC called j721e with a j721e-evm.
>
> Fix up this naming here.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
next prev parent reply other threads:[~2022-03-29 4:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 18:41 [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm Andrew Davis
2022-03-25 18:41 ` [meta-ti][master][PATCH 2/4] meta-ti-bsp: add SoC families for the J7 SoCs Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 18:41 ` [meta-ti][master][PATCH 3/4] ti-img-rogue-umlibs: only the j721e SoC is currently supported Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 18:41 ` [meta-ti][master][PATCH 4/4] ti-sgx-ddk-um: only the am65xx member of the k3 family is supported Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 19:23 ` [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm Denys Dmytriyenko
2022-03-25 19:38 ` Andrew Davis
2022-03-29 4:48 ` Denys Dmytriyenko
2022-03-29 4:49 ` Denys Dmytriyenko [this message]
2022-03-29 12:39 ` Ryan Eatmon
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=20220329044933.GN23554@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=detheridge@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@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.