From: Nishanth Menon <menon.nishanth@gmail.com>
To: kbuild test robot <lkp@intel.com>, Nishanth Menon <nm@ti.com>
Cc: linux-kernel@vger.kernel.org, kbuild-all@01.org,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] reset: Introduce static inline dummy function when CONFIG_RESET_CONTROLLER
Date: Tue, 01 Dec 2015 10:07:45 -0600 [thread overview]
Message-ID: <565DC5D1.2080809@gmail.com> (raw)
In-Reply-To: <201512012339.srrujPao%fengguang.wu@intel.com>
On 12/01/2015 09:56 AM, kbuild test robot wrote:
> Hi Nishanth,
>
> [auto build test ERROR on v4.4-rc3]
> [also build test ERROR on next-20151127]
>
> url: https://github.com/0day-ci/linux/commits/Nishanth-Menon/reset-Introduce-static-inline-dummy-function-when-CONFIG_RESET_CONTROLLER/20151201-233708
> config: i386-randconfig-n0-201548 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> In file included from drivers/reset/core.c:18:0:
>>> include/linux/reset-controller.h:1:0: error: unterminated #ifndef
> #ifndef _LINUX_RESET_CONTROLLER_H_
> ^
Uggh.. thanks kbot... :).. my bad.. last minute whitespace editscan end
up deleting #endifs :(
While at it, will fix $subject as well.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-12-01 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 15:34 [PATCH] reset: Introduce static inline dummy function when CONFIG_RESET_CONTROLLER Nishanth Menon
2015-12-01 15:56 ` kbuild test robot
2015-12-01 16:07 ` Nishanth Menon [this message]
2015-12-01 16:38 ` [PATCH V2] reset: Introduce static inline dummy function when CONFIG_RESET_CONTROLLER is not set Nishanth Menon
2015-12-01 20:20 ` [PATCH] reset: Introduce static inline dummy function when CONFIG_RESET_CONTROLLER kbuild test robot
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=565DC5D1.2080809@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
/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).