diff options
| author | Colin Ian King <colin.king@canonical.com> | 2017-12-04 18:08:15 +0100 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2017-12-07 09:59:39 +0100 |
| commit | 33b6cb58cbb6c872ebf874d8017c27aaa2130928 (patch) | |
| tree | 4f8565eec65665f69f9a6ee3339a2476459da6af /Documentation | |
| parent | pinctrl: gemini: Support drive strength setting (diff) | |
| download | linux-33b6cb58cbb6c872ebf874d8017c27aaa2130928.tar.xz linux-33b6cb58cbb6c872ebf874d8017c27aaa2130928.zip | |
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>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions