From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: kbuild test robot <lkp@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
kbuild-all@01.org, "David E . Box" <david.e.box@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [kbuild-all] [PATCH 1/3] pinctrl: intel: Add support for hardware debouncer
Date: Fri, 3 Feb 2017 10:34:44 +0800 [thread overview]
Message-ID: <20170203023444.GD23647@yexl-desktop> (raw)
In-Reply-To: <20170127204905.GZ17297@lahna.fi.intel.com>
On 01/27, Mika Westerberg wrote:
>On Fri, Jan 27, 2017 at 07:51:03PM +0800, kbuild test robot wrote:
>> Hi Mika,
>>
>> [auto build test ERROR on pinctrl/for-next]
>> [also build test ERROR on v4.10-rc5 next-20170125]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>
>> url: https://github.com/0day-ci/linux/commits/Mika-Westerberg/pinctrl-intel-Add-support-for-hardware-debouncer/20170127-181144
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git for-next
>> config: x86_64-randconfig-s5-01271855 (attached as .config)
>> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
>> reproduce:
>> # save the attached .config to linux build tree
>> make ARCH=x86_64
>>
>> All errors (new ones prefixed by >>):
>>
>> >> drivers/pinctrl/intel/pinctrl-intel.c:754:2: error: unknown field 'set_config' specified in initializer
>> .set_config = gpiochip_generic_config,
>> ^
>> >> drivers/pinctrl/intel/pinctrl-intel.c:754:16: error: 'gpiochip_generic_config' undeclared here (not in a function)
>> .set_config = gpiochip_generic_config,
>> ^~~~~~~~~~~~~~~~~~~~~~~
>
>Dear kbuild robot, thanks for spotting this. However, in this case the
>series is based on top of linux-pinctrl.git/devel branch which should
>include the missing changes.
>
Thanks for the message, we've added the devel branch as the apply base to fix it.
Thanks,
Xiaolong
>Keep up the good work, though :)
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2017-02-03 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:07 [PATCH 0/3] pinctrl: Add support for Intel Gemini Lake Mika Westerberg
2017-01-27 10:07 ` [PATCH 1/3] pinctrl: intel: Add support for hardware debouncer Mika Westerberg
2017-01-27 11:51 ` kbuild test robot
2017-01-27 20:49 ` Mika Westerberg
2017-02-03 2:34 ` Ye Xiaolong [this message]
2017-01-30 14:03 ` Linus Walleij
2017-01-30 15:38 ` Mika Westerberg
2017-01-27 10:07 ` [PATCH 2/3] pinctrl: intel: Add support for 1k additional pull-down Mika Westerberg
2017-01-30 14:05 ` Linus Walleij
2017-01-27 10:07 ` [PATCH 3/3] pinctrl: intel: Add Intel Gemini Lake pin controller support Mika Westerberg
2017-01-30 14:06 ` 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=20170203023444.GD23647@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).