From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: mmotm 2019-07-04-15-01 uploaded (gpu/drm/i915/oa/)
Date: Thu, 4 Jul 2019 18:19:43 -0700 [thread overview]
Message-ID: <63db23ac-c642-3e0c-58a4-81df991ad637@infradead.org> (raw)
In-Reply-To: <80bf2204-558a-6d3f-c493-bf17b891fc8a@infradead.org>
On 7/4/19 6:09 PM, Randy Dunlap wrote:
> On 7/4/19 3:01 PM, akpm@linux-foundation.org wrote:
>> The mm-of-the-moment snapshot 2019-07-04-15-01 has been uploaded to
>>
>> http://www.ozlabs.org/~akpm/mmotm/
>>
>> mmotm-readme.txt says
>>
>> README for mm-of-the-moment:
>>
>> http://www.ozlabs.org/~akpm/mmotm/
>
> I get a lot of these but don't see/know what causes them:
>
> ../scripts/Makefile.build:42: ../drivers/gpu/drm/i915/oa/Makefile: No such file or directory
> make[6]: *** No rule to make target '../drivers/gpu/drm/i915/oa/Makefile'. Stop.
> ../scripts/Makefile.build:498: recipe for target 'drivers/gpu/drm/i915/oa' failed
> make[5]: *** [drivers/gpu/drm/i915/oa] Error 2
> ../scripts/Makefile.build:498: recipe for target 'drivers/gpu/drm/i915' failed
>
[+ linux-kbuild]
It seems to have something to do with "modules.order".
But!!!
# CONFIG_DRM_I915 it not set
--
~Randy
next prev parent reply other threads:[~2019-07-05 1:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 22:01 mmotm 2019-07-04-15-01 uploaded akpm
2019-07-05 1:09 ` mmotm 2019-07-04-15-01 uploaded (gpu/drm/i915/oa/) Randy Dunlap
2019-07-05 1:19 ` Randy Dunlap [this message]
2019-07-05 3:05 ` Masahiro Yamada
2019-07-05 3:09 ` Masahiro Yamada
2019-07-05 3:23 ` Randy Dunlap
2019-07-05 3:44 ` Masahiro Yamada
2019-07-05 4:09 ` Randy Dunlap
2019-07-31 13:21 ` Jani Nikula
2019-07-05 3:14 ` Stephen Rothwell
2019-07-05 5:09 ` Andrew Morton
2019-07-05 5:22 ` Joe Perches
2019-07-05 5:29 ` Andrew Morton
2019-07-05 3:01 ` mmotm 2019-07-04-15-01 uploaded (mm/vmscan.c) Randy Dunlap
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=63db23ac-c642-3e0c-58a4-81df991ad637@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).