summaryrefslogtreecommitdiff
path: root/upstream-layers/meta-openembedded/meta-python/recipes-devtools/python/python3-dnspython
diff options
context:
space:
mode:
authorSean He <sean.he.wiwynn@gmail.com>2026-10-08 13:09:05 +0300
committerAmithash Prasad <amithash@meta.com>2026-10-21 21:21:45 +0300
commita3aa2f0be8b423533c491369c622f2180aa9d78a (patch)
treefd0a81ebfed7d4023b5bd2dc454dcdbc45029604 /upstream-layers/meta-openembedded/meta-python/recipes-devtools/python/python3-dnspython
parent1afc2262034c72c03fecc3a20ee6423c2520149b (diff)
downloadopenbmc-a3aa2f0be8b423533c491369c622f2180aa9d78a.tar.xz
meta-facebook: yosemite4: drop host DIMM inventory settings template
Removes the settings-template YAML that unconditionally pre-created 20 DIMM objects per slot, now superseded by Notify-based object creation. Motivation: yosemite4-temporary-host-dimm-inventory.yml pre-created 12 Sentinel Dome + 8 Wailua Falls DIMM objects per slot via phosphor-settingsd, for all 8 slots regardless of T1/T2 config [1] -- the YAML is expanded at build time, but board config is only known per slot at runtime, so no build-time selection could be correct. Downstream service replaces this with per-slot calls to phosphor-inventory-manager's Notify, which only creates an object for a DIMM actually reports, and already carries a local SETTINGS_HOST_TEMPLATES:remove to stop consuming this template. This change removes the template at its source instead of leaving that downstream override as the only thing suppressing it. Reference: [1] https://gerrit.openbmc.org/c/openbmc/openbmc/+/89805 Tested: - Build code: pass - Confirm xyz.openbmc_project.Settings.service no longer creates DIMM objects for any slot: pass Change-Id: I54f54dd0195c9e4071626a06bc49f1e485f4cb56 Signed-off-by: Sean He <sean.he.wiwynn@gmail.com>
Diffstat (limited to 'upstream-layers/meta-openembedded/meta-python/recipes-devtools/python/python3-dnspython')
0 files changed, 0 insertions, 0 deletions