From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the drivers-memory tree
Date: Mon, 27 Jul 2020 21:36:41 +1000 [thread overview]
Message-ID: <20200727213641.3491e3d1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
Hi all,
After merging the drivers-memory tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/memory/omap-gpmc.c:36:10: fatal error: asm/mach-types.h: No such file or directory
36 | #include <asm/mach-types.h>
| ^~~~~~~~~~~~~~~~~~
Caused by commit
99b42df9d57e ("memory: Enable compile testing for most of the drivers")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-27 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:36 Stephen Rothwell [this message]
2020-07-27 11:49 ` linux-next: build failure after merge of the drivers-memory tree Krzysztof Kozlowski
2020-11-08 23:23 Stephen Rothwell
2020-11-09 1:01 ` Dmitry Osipenko
2020-11-09 8:04 ` Krzysztof Kozlowski
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=20200727213641.3491e3d1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).