From: Uwe Kleine-König <redacted>
Date: Tue, 31 Mar 2015 22:08:45 +0200

I still think assigning directly to priv->gpiod_reset would fine
because having the priv->gpiod_reset NULL is neither more nor less
right that ERR_PTR(-ESOMETHING).

You really want to push my buttons don't you? :-/

What if someone adds a new resource allocation after this thing and
then adds an unwind path where something has to be done to the GPIOD
as part of cleanup?

What does your error pointer cause to happen to an unsuspecting person
creating such a change?

Why isn't this obvious to you as a good coding practice that is
future proof against any changes to this code?