Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 8 Nov 2022 10:40:33 +0100 | Subject | Re: Coverity: gpmc_is_valid_waitpin(): Control flow issues | From | Krzysztof Kozlowski <> |
| |
On 08/11/2022 09:15, Niedermayr, BENEDIKT wrote:
>>> Another alternative with less churn is to leave them as u32 >>> but make GPMC_WAITPIN_INVALID set to a large positive number. >> Ok, I will fix that. >> Do I need to send a new fix-patch on top the current patch series? >> Or should I just send only the bugfix-patch for the coverity-bot? >> > Sorry, another Question: > Is it somehow possible to check locally if the bugfix actually fixed the bug, before I submit the patch?
I think only if you have Coverity somewhere in your company set for testing kernel...
Best regards, Krzysztof
| ![\](/images/icornerr.gif) |