Clarify comment how manifests are combined.
ODM manifest pieces augment the core manifest. Only when the old odm
manifest location is used does an override happen. This is covered by
items (3) and (4) in the doc this CL edits.
Change-Id: I8d5cd60a65d57210fa744e02106601da50573efe
Fixes: 117533120
Test: N/A
diff --git a/VintfObject.cpp b/VintfObject.cpp
index aed9745..47480a4 100644
--- a/VintfObject.cpp
+++ b/VintfObject.cpp
@@ -232,7 +232,8 @@
// 3. ODM manifest (optional) + odm fragments
// 4. /vendor/manifest.xml (legacy, no fragments)
// where:
-// A + B means adding <hal> tags from B to A (so that <hal>s from B can override A)
+// A + B means unioning <hal> tags from A and B. If B declares an override, then this takes priority
+// over A.
status_t VintfObject::fetchDeviceHalManifest(HalManifest* out, std::string* error) {
status_t vendorStatus = fetchOneHalManifest(kVendorManifest, out, error);
if (vendorStatus != OK && vendorStatus != NAME_NOT_FOUND) {
