When the kernel function name is used as a macro argument, the migration result may be incorrect. You need to verify the definition of the macro.

When a kernel function call is used in a macro definition and the function name is passed as a macro argument, the tool cannot determine the type of function parameters. This may lead to incorrectly generated DPC++ code.

Review the kernel call inside the macro definition and adjust it manually, if needed.