Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-gpio@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: pxa: guard sub-directory with CONFIG_PINCTRL_PXA
Date: Sat, 23 Jan 2016 23:22:02 +0100	[thread overview]
Message-ID: <87bn8caqd1.fsf@belgarion.home> (raw)
In-Reply-To: <CAK7LNATA6wZUC_ASNHVbACD5rGFR9vZpRbfXaz7dfsne84nDfQ@mail.gmail.com> (Masahiro Yamada's message of "Sun, 24 Jan 2016 04:35:19 +0900")

Masahiro Yamada <yamada.masahiro@socionext.com> writes:

> 2016-01-24 2:56 GMT+09:00 kbuild test robot <lkp@intel.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,
It was, and runtime tested also, in a builtin form. It was not activated in the
kernel at the arch/arm pxa architecture level would be a better statement.

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

> I hope [2] will be applied before this patch
> in order to suppress the complaint by the kbuild test robot.
Let's see what Linus thinks of it.

Cheers.

-- 
Robert

  reply	other threads:[~2016-01-23 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 15:31 [PATCH] pinctrl: pxa: guard sub-directory with CONFIG_PINCTRL_PXA Masahiro Yamada
2016-01-23 17:56 ` kbuild test robot
2016-01-23 19:35   ` Masahiro Yamada
2016-01-23 22:22     ` Robert Jarzmik [this message]
2016-01-28 10:24 ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bn8caqd1.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox