summaryrefslogtreecommitdiff
path: root/drivers/pinctrl/pinctrl-xway.c
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2016-07-19 03:30:30 +0300
committerLinus Walleij <linus.walleij@linaro.org>2016-07-22 18:26:10 +0300
commitb9416498d68980387ff7094785d9a49ebfa53f10 (patch)
tree81f9aba3a03f35cdf2f5500a41161a7de2a2af06 /drivers/pinctrl/pinctrl-xway.c
parentf58de3d96a73e05b5bb67be517e6e87c6234fef0 (diff)
downloadlinux-b9416498d68980387ff7094785d9a49ebfa53f10.tar.xz
Revert "pinctrl: amd: make it explicitly non-modular"
This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda. This patch was in my queue at the same time that a conversion of the same driver from bool --> tristate was pending and merged. That is commit 337ea0fb1535 ("pinctrl: Turn AMD support to tristate") Normally the conflict would show up in the build coverage I do, however in this case an avoidable instance of linux/module.h in linux/gpio/driver.h (!) causes the build failure to be masked and instead the tristate gets built-in even for selected "=m". In working on removing module.h from driver.h this issue was then revealed (along with other implicit module.h assumptions in gpio, and mfd -- which will be fixed separately.) Cc: linux-gpio@vger.kernel.org Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Acked-by: Jean Delvare <jdelvare@suse.de> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/pinctrl/pinctrl-xway.c')
0 files changed, 0 insertions, 0 deletions