[PATCH v1 1/1] spi: npcm: fix uninitialized 'val' warning in receive function
broonie at kernel.org
Wed Nov 21 00:02:10 AEDT 2018
On Tue, Nov 20, 2018 at 12:51:19PM +0200, Tomer Maimon wrote:
> We just tried to reduce the number of lines to minimum, so we have debug it
> quite a lot (with all the numbers that can
> get from priv->tx_bytes) and the only numbers that minimum function return
> are 0, 1 or 2.
> But in the end of the day, we don't have an issue with your solution as
> long it will be done also in the transfer function.
In general it's better to have the code be obviously correct than to try
to push down the line count - it saves people the effort of figuring out
if things are safe every time they look at it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the openbmc