Nouveau - May 2020 - drm/nouveau/clk/gm20b: Fix memory leak in gm20b_clk_new()

> 
> > It's the same when gm20b_clk_new() returns from elsewhere
following this call.
> 
> I suggest to reconsider the interpretation of the software situation once
more.
> Can it be that the allocated clock object should be kept usable even after
> a successful return from this function?
> 
It's possible that we expect an usable clk pointer, though I could not find
the exact usage yet. For security, I will release this pointer only on error 
paths in this function.
> 
> Would you like to add the tag ?Fixes? to the commit message?
> 
Thank you for your advice! I will add this tag in the next version of patch.

Regards,
Dinghao

> 
> > For security, I will release this pointer only on error paths in this
function.
> 
> Do you tend to release objects (which are referenced by pointers)?
> 
I just found that clk is referenced by pclk in this function. When clk is freed,
pclk will be allocated in gm20b_clk_new_speedo0(). Thus we should not release
clk
in this function and there is no bug here. Thank you for reminding me!

Regards,
Dinghao