pinctrl: intel: ensure error return ret is initialized
authorColin Ian King <colin.king@canonical.com>
Mon, 4 Dec 2017 17:08:15 +0000 (17:08 +0000)
committerLinus Walleij <linus.walleij@linaro.org>
Thu, 7 Dec 2017 08:59:39 +0000 (09:59 +0100)
commit33b6cb58cbb6c872ebf874d8017c27aaa2130928
tree4f8565eec65665f69f9a6ee3339a2476459da6af
parentad63da85f45fa55c270e5681e9b985605ec51f8d
pinctrl: intel: ensure error return ret is initialized

In the (unlikely) event that community->ngpps is zero, or if every
gpp->gpio_base is less than zero, then an ininitialized value in
ret is returned by function intel_gpio_add_pin_ranges. Fix this by
ensuring ret is initialized to zero.  It's a moot point, but I think
it is worthwhile ensuring this corner case is fixed.

Detected by CoverityScan, CID#1462415 ("Uninitialized scalar variable")

Fixes: a60eac3239f0 ("pinctrl: intel: Allow custom GPIO base for pad groups")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
drivers/pinctrl/intel/pinctrl-intel.c