linux-kernel - Re: [PATCH] pinctrl: pxa: guard sub-directory with CONFIG_PINCTRL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNATA6wZUC_ASNHVbACD5rGFR9vZpRbfXaz7dfsne84nDfQ@mail.gmail.com>
Date:	Sun, 24 Jan 2016 04:35:19 +0900
From:	Masahiro Yamada <yamada.masahiro@...ionext.com>
To:	linux-gpio@...r.kernel.org
Cc:	Robert Jarzmik <robert.jarzmik@...e.fr>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] pinctrl: pxa: guard sub-directory with CONFIG_PINCTRL_PXA

2016-01-24 2:56 GMT+09:00 kbuild test robot <lkp@...el.com>:
> Hi Masahiro,
>
> [auto build test ERROR on next-20160122]
> [cannot apply to v4.4-rc8 v4.4-rc7 v4.4-rc6 v4.4]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url:    https://github.com/0day-ci/linux/commits/Masahiro-Yamada/pinctrl-pxa-guard-sub-directory-with-CONFIG_PINCTRL_PXA/20160123-233501
> config: x86_64-allmodconfig (attached as .config)
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "pxa2xx_pinctrl_init" [drivers/pinctrl/pxa/pinctrl-pxa27x.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


driver/pinctrl/pxa/ has never been compile-tested before,
and it has just unveiled some issues of this driver.


[1]  driver/pinctrl/pxa/ has not been activated yet,
so I posted this:
https://patchwork.kernel.org/patch/8097771/


[2]  this driver is declared as tristate, but it cannot be a module,
so I posted this:
https://patchwork.kernel.org/patch/8097781/




I hope [2] will be applied before this patch
in order to suppress the complaint by the kbuild test robot.



-- 
Best Regards
Masahiro Yamada