PEL: Fixing wrong callout of reference target
-The target provided in HwCallout structure is, only a reference target
to find the actual hardware target need to be called out. So, this
target should not be called out.
Signed-off-by: Rajees P P <rajerpp1@in.ibm.com>
Change-Id: Ibf58b47ceaed051bc88481c631844553d671d409
diff --git a/extensions/openpower-pels/fapi_data_process.cpp b/extensions/openpower-pels/fapi_data_process.cpp
index 6ac6ebd..a47b7fe 100644
--- a/extensions/openpower-pels/fapi_data_process.cpp
+++ b/extensions/openpower-pels/fapi_data_process.cpp
@@ -266,21 +266,6 @@
ffdcUserData.emplace_back(
std::string(keyPrefix.str()).append("CLK_POS"),
std::to_string(hwCallout.clkPos));
-
- json jsonCalloutData;
- jsonCalloutData["LocationCode"] = locationCode;
- std::string pelPriority =
- getPelPriority(hwCallout.callout_priority);
- jsonCalloutData["Priority"] = pelPriority;
-
- if (targetInfo.mruId != 0)
- {
- jsonCalloutData["MRUs"] = json::array({
- {{"ID", targetInfo.mruId}, {"Priority", pelPriority}},
- });
- }
-
- pelJSONFmtCalloutDataList.emplace_back(jsonCalloutData);
});
// Adding CDG (callout, deconfigure and guard) targets details