From: Fengguang Wu <fengguang.wu@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Christopher Heiny <cheiny@synaptics.com>, linux-input@vger.kernel.org
Subject: Re: [input:synaptics-rmi4 4/11] make[4]: *** No rule to make target `drivers/input/rmi4/rmi_f01.o', needed by `drivers/input/rmi4/built-in.o'.
Date: Wed, 28 Nov 2012 17:37:54 +0800 [thread overview]
Message-ID: <20121128093754.GB23422@localhost> (raw)
In-Reply-To: <20121128063334.GB23378@core.coreip.homeip.net>
On Tue, Nov 27, 2012 at 10:33:34PM -0800, Dmitry Torokhov wrote:
> Hi,
>
> On Wed, Nov 28, 2012 at 02:15:57PM +0800, kbuild test robot wrote:
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git synaptics-rmi4
> > head: 0af25383d395fb5ece54b79d12d06138bf8b9836
> > commit: 49c28c0062548243aa0e15f181098af34bab9712 [4/11] Input: input/rmi4 - Config files and makefiles
> > config: make ARCH=x86_64 allmodconfig
> >
> > Note: the input/synaptics-rmi4 HEAD 0af2538 builds fine.
> > It only hurts bisectibility.
>
> This branch is gonna have a few errors for a while, I am not sure if we
> want to exclude it or just ignore the errors for now....
Dmitry, reported errors will be remembered by the build system and not
reported again.
However if you want to avoid possible new errors being reported, you
may put this line to any commit of the branch
Dont-Auto-Build
The build script will then skip the whole branch.
And remember to remove that line by the time you think it suitable for
testing again. ;)
Thanks,
Fengguang
prev parent reply other threads:[~2012-11-28 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 6:15 [input:synaptics-rmi4 4/11] make[4]: *** No rule to make target `drivers/input/rmi4/rmi_f01.o', needed by `drivers/input/rmi4/built-in.o' kbuild test robot
2012-11-28 6:33 ` Dmitry Torokhov
2012-11-28 9:37 ` Fengguang Wu [this message]
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=20121128093754.GB23422@localhost \
--to=fengguang.wu@intel.com \
--cc=cheiny@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/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).