From: Daniel Vetter <daniel@ffwll.ch>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
dri-devel@lists.freedesktop.org, kbuild-all@01.org
Subject: Re: [drm-intel:drm-intel-nightly 341/365] drivers/gpu/drm//selftests/test-drm_mm.c:58:1: fatal error: opening dependency file drivers/gpu/drm//selftests/.test-drm_mm.o.d: No such file or directory
Date: Tue, 27 Dec 2016 19:46:55 +0100 [thread overview]
Message-ID: <20161227184655.GD347@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <201612280004.IgMKNitc%fengguang.wu@intel.com>
On Wed, Dec 28, 2016 at 12:57:07AM +0800, kbuild test robot wrote:
> tree: git://anongit.freedesktop.org/drm-intel drm-intel-nightly
> head: 0d15e733fab5dd48154dda2bebdacd1d87069d08
> commit: 50f0033d1a0f3a8e9eed09ab68067fbb57b0669d [341/365] drm: Add some kselftests for the DRM range manager (struct drm_mm)
> config: arm-allmodconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 50f0033d1a0f3a8e9eed09ab68067fbb57b0669d
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> >> drivers/gpu/drm//selftests/test-drm_mm.c:58:1: fatal error: opening dependency file drivers/gpu/drm//selftests/.test-drm_mm.o.d: No such file or directory
> MODULE_LICENSE("GPL");
> ^~~~~~~~~~~~~~
> compilation terminated.
Hm, it compiles fine here. Is there anything different than normal in your
build setup? Like compiling to a different target using O=$output_path?
-Daniel
>
> vim +58 drivers/gpu/drm//selftests/test-drm_mm.c
>
> 42
> 43 return err > 0 ? 0 : err;
> 44 }
> 45
> 46 static void __exit test_drm_mm_exit(void)
> 47 {
> 48 }
> 49
> 50 module_init(test_drm_mm_init);
> 51 module_exit(test_drm_mm_exit);
> 52
> 53 module_param(random_seed, uint, 0400);
> 54 module_param(max_iterations, uint, 0400);
> 55 module_param(max_prime, uint, 0400);
> 56
> 57 MODULE_AUTHOR("Intel Corporation");
> > 58 MODULE_LICENSE("GPL");
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-27 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 16:57 [drm-intel:drm-intel-nightly 341/365] drivers/gpu/drm//selftests/test-drm_mm.c:58:1: fatal error: opening dependency file drivers/gpu/drm//selftests/.test-drm_mm.o.d: No such file or directory kbuild test robot
2016-12-27 18:46 ` Daniel Vetter [this message]
2016-12-28 9:38 ` Daniel Vetter
2016-12-28 14:37 ` Fengguang Wu
2016-12-28 14:55 ` Chris Wilson
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=20161227184655.GD347@dvetter-linux.ger.corp.intel.com \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengguang.wu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kbuild-all@01.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