Pass the correct TokenNumber into a CallbackOnSet notification function. The value being passed in was off by 1.

This would not normally cause an issue because the correct notification function was being called.  There is only an issue if the same notification function is being used for multiple tokens, and the notification function needs to use the TokenNumber parameter to determine which token setting caused the callback function to be called.


git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@9980 6f19259b-4bc3-4df7-8a09-765794883524

1 files changed, 1 insertions, 1 deletions

diff --git a/MdeModulePkg/Universal/PCD/Pei/Service.c b/MdeModulePkg/Universal/PCD/Pei/Service.c
index ec91699182..ab3059c735 100644
--- a/MdeModulePkg/Universal/PCD/Pei/Service.c
+++ b/MdeModulePkg/Universal/PCD/Pei/Service.c
@@ -305,7 +305,7 @@ InvokeCallbackOnSet (
   for (Idx = 0; Idx < PcdGet32 (PcdMaxPeiPcdCallBackNumberPerPcdEntry); Idx++) {

     if (CallbackTable[Idx] != NULL) {

       CallbackTable[Idx] (Guid,

-                          (Guid == NULL)? TokenNumber: ExTokenNumber,

+                          (Guid == NULL) ? (TokenNumber + 1) : ExTokenNumber,

                           Data,

                           Size

                           );