As per spec, 0th bit is set when the controller detects an overlapping firmware/boot partition image update command sequence due to processing a command from an Admin Submission Queue on a controller and the 1st bit is set due to processing the command from Management Endpoint. So, fixed the MUD result message.
As per spec, 0th bit is set when the controller detects an overlapping firmware/boot partition image update command sequence due to processing a command from an Admin Submission Queue on a controller and the 1st bit is set due to processing the command from Management Endpoint. So, fixed the MUD result message.