Re: GPU-DRM-Savage: Less function calls in savage_bci_cmdbuf() after error detection
From: SF Markus Elfring
Date: Wed Oct 12 2016 - 08:11:37 EST
>> Date: Thu, 18 Aug 2016 21:28:58 +0200
>> The kfree() function was called in a few cases by the
>> savage_bci_cmdbuf() function during error handling
>> even if a passed variable contained a null pointer.
>> Adjust jump targets according to the Linux coding style convention.
>> Signed-off-by: Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
> Not sure this is worth it, I'll pass. Patch 1 merged.
Unfortunately, it seems that this selection of only one update step
from this small patch series has got unwanted consequences.
Will the update suggestion “[patch] drm/savage: dereferencing an error pointer”
by Dan Carpenter (from today) trigger further software development discussions?
Will an update step like “[PATCH 2/2] GPU-DRM-Savage: Less function calls in
savage_bci_cmdbuf() after error detection” (from 2016-08-18) become worth
for related consideratons once more?