From: "Ming Liu" <liu.ming50@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: stefan.agner@toradex.com, sergio.prado@toradex.com,
max.krummenacher@toradex.com, anuj.mittal@intel.com,
Ming Liu <liu.ming50@gmail.com>
Subject: [OE-core] [dunfell] [PATCH V2 0/4] libubootenv: uprev to v0.3
Date: Wed, 26 Aug 2020 19:48:49 +0200 [thread overview]
Message-ID: <20200826174853.8838-1-liu.ming50@gmail.com> (raw)
From: Ming Liu <liu.ming50@gmail.com>
Cherry pick the patches from master to upgrade libubootenv 0.2 -> 0.3.
Since libubootenv 0.2 is sort of buggy, it lacks of a lot of
bug/regression/security fixes which has been included in 0.3.
Changes in patch set V2:
1 Let libubootenv inherit uboot-config to get
UBOOT_MAECHINE/UBOOT_CONFIG sanity check.
Ming Liu (4):
conf/machine: set UBOOT_MACHINE for qemumips and qemumips64
multilib.conf: add u-boot to NON_MULTILIB_RECIPES
libubootenv: uprev to v0.3
libubootenv: inherit uboot-config
meta/conf/machine/qemumips.conf | 2 ++
meta/conf/machine/qemumips64.conf | 2 ++
meta/conf/multilib.conf | 2 +-
.../u-boot/{libubootenv_0.2.bb => libubootenv_0.3.bb} | 9 ++++++---
4 files changed, 11 insertions(+), 4 deletions(-)
rename meta/recipes-bsp/u-boot/{libubootenv_0.2.bb => libubootenv_0.3.bb} (78%)
--
2.28.0
next reply other threads:[~2020-08-26 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 17:48 Ming Liu [this message]
2020-08-26 17:48 ` [OE-core] [dunfell] [PATCH V2 1/4] conf/machine: set UBOOT_MACHINE for qemumips and qemumips64 Ming Liu
2020-08-26 17:48 ` [OE-core] [dunfell] [PATCH V2 2/4] multilib.conf: add u-boot to NON_MULTILIB_RECIPES Ming Liu
2020-08-26 17:48 ` [OE-core] [dunfell] [PATCH V2 3/4] libubootenv: uprev to v0.3 Ming Liu
2020-08-26 17:48 ` [OE-core] [dunfell] [PATCH V2 4/4] libubootenv: inherit uboot-config Ming Liu
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=20200826174853.8838-1-liu.ming50@gmail.com \
--to=liu.ming50@gmail.com \
--cc=anuj.mittal@intel.com \
--cc=max.krummenacher@toradex.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sergio.prado@toradex.com \
--cc=stefan.agner@toradex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox