for the Request parameter\r
would result in this type of\r
error. The Progress parameter\r
- is set to NULL. EFI_NOT_FOUND\r
- Routing data doesn't match any\r
+ is set to NULL. \r
+ \r
+ @retval EFI_NOT_FOUND Routing data doesn't match any\r
known driver. Progress set to\r
the "G" in "GUID" of the\r
routing header that doesn't\r
@retval EFI_NOT_FOUND Target for the specified routing data\r
was not found. Progress points to the\r
'G' in "GUID" of the errant routing\r
- data. EFI_DEVICE_ERROR Block not large\r
- enough. Progress undefined.\r
+ data. \r
+ @retval EFI_DEVICE_ERROR Block not large enough. Progress undefined.\r
\r
@retval EFI_INVALID_PARAMETER Encountered non <BlockName>\r
formatted string. Block is\r
\r
@retval EFI_SUCCESS The request succeeded. Progress points to the null\r
terminator at the end of the ConfigResp string.\r
- @retval EFI_OUT_OF_RESOURCES Not enough memory to allocate Config. Progress\r
+ @retval EFI_OUT_OF_RESOURCES Not enough memory to allocate Config. Progress\r
points to the first character of ConfigResp.\r
@retval EFI_INVALID_PARAMETER Passing in a NULL for the ConfigResp or\r
Block parameter would result in this type of\r