From: Thierry Reding <treding@nvidia.com>
To: Abhishek Sahu <absahu@codeaurora.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 4.14.rc-2 fails to build with arm64 defconfig
Date: Tue, 26 Sep 2017 11:15:22 +0200 [thread overview]
Message-ID: <20170926091521.GA32224@ulmo> (raw)
In-Reply-To: <59ab19fb4a4e16ff97154ea9bed97e0f@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Tue, Sep 26, 2017 at 02:26:06PM +0530, Abhishek Sahu wrote:
> Hi Thierry,
>
> The 4.14 arm64 defconfig is broken with following error
>
> In file included from drivers/gpu/drm/tegra/trace.h:68:0,
> from drivers/gpu/drm/tegra/trace.c:2:
> ./include/trace/define_trace.h:88:43: fatal error: ./trace.h: No such file
> or directory
> #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
> ^
> compilation terminated.
>
> It seems already you did the fix for this error which is available in next
> tree.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20170926&id=c79dc3b7fd093fb3b312281f93b405a60543eeaa
> https://lkml.org/lkml/2017/8/24/206
>
> Could we get this fix merged in next available RC for 4.14 since arm64
> defconfig is not building with default configs.
Thanks for the reminder. I had been travelling for the past two weeks
and not gotten around to send the fix out. It's in drm-misc-fixes now,
so should find its way into the v4.14-rc3.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-09-26 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 8:56 4.14.rc-2 fails to build with arm64 defconfig Abhishek Sahu
2017-09-26 9:15 ` Thierry Reding [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=20170926091521.GA32224@ulmo \
--to=treding@nvidia.com \
--cc=absahu@codeaurora.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.