From: "Christopher Larson" <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/2] Exclude OVERRIDES from vardeps for a couple funcs
Date: Thu, 10 Dec 2020 13:28:01 -0700 [thread overview]
Message-ID: <cover.1607630988.git.kergoth@gmail.com> (raw)
These functions are primarily *appending* configuration entries to the
overrides, they only get it to ensure it's set at all, so doesn't belong
in the vardeps. Having a dependency on OVERRIDES means you cannot use a
bbclass like distrooverrides without changing the signatures of recipes
using this class.
Christopher Larson (2):
grub-efi-cfg: exclude OVERRIDES from build_efi_cfg vardeps
uboot-extlinux-config: exclude OVERRIDES from
do_create_extlinux_config vardeps
meta/classes/grub-efi-cfg.bbclass | 1 +
meta/classes/uboot-extlinux-config.bbclass | 1 +
2 files changed, 2 insertions(+)
--
2.29.2
next reply other threads:[~2020-12-10 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 20:28 Christopher Larson [this message]
2020-12-10 20:28 ` [PATCH 1/2] grub-efi-cfg: exclude OVERRIDES from build_efi_cfg vardeps Christopher Larson
2020-12-10 20:28 ` [PATCH 2/2] uboot-extlinux-config: exclude OVERRIDES from do_create_extlinux_config vardeps Christopher Larson
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=cover.1607630988.git.kergoth@gmail.com \
--to=kergoth@gmail.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
/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