From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH v2] u-boot: Change depends from lzop to lzo
Date: Thu, 13 Oct 2022 15:24:40 -0400 [thread overview]
Message-ID: <20221013192440.GJ22689@denix.org> (raw)
In-Reply-To: <20221013182602.9318-1-reatmon@ti.com>
On Thu, Oct 13, 2022 at 01:26:02PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> lzop has disappeared from upstream master, but lzo is there.
lzop is actually a compression tool, while lzo is just a library.
so, I don't believe this change is correct/complete.
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> v2: Fixed typo lzpo -> lzop
>
> meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> index d29c80cf..88018541 100644
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> @@ -23,7 +23,7 @@ SRC_URI = "${UBOOT_GIT_URI};protocol=${UBOOT_GIT_PROTOCOL};branch=${BRANCH}"
> PV:append = "+git${SRCPV}"
>
> # u-boot needs devtree compiler to parse dts files
> -DEPENDS += "dtc-native bc-native lzop-native flex-native bison-native python3-setuptools-native"
> +DEPENDS += "dtc-native bc-native lzo-native flex-native bison-native python3-setuptools-native"
>
> DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f"
>
> --
> 2.17.1
next prev parent reply other threads:[~2022-10-13 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:26 [meta-ti][master][PATCH v2] u-boot: Change depends from lzop to lzo Ryan Eatmon
2022-10-13 19:24 ` Denys Dmytriyenko [this message]
2022-10-13 20:10 ` Andrew Davis
2022-10-13 20:15 ` Ryan Eatmon
2022-10-13 20:38 ` 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=20221013192440.GJ22689@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--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.