From: Thierry Reding <treding@nvidia.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next-20170823 failed to build for arm64/defconfig
Date: Thu, 24 Aug 2017 10:34:51 +0200 [thread overview]
Message-ID: <20170824083451.GA25455@ulmo> (raw)
In-Reply-To: <20170823085339.GA3825@ulmo>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On Wed, Aug 23, 2017 at 10:53:39AM +0200, Thierry Reding wrote:
> On Wed, Aug 23, 2017 at 04:19:55PM +0800, Shawn Lin wrote:
> > Hi Thierry and Stephen,
> >
> > commit 67e04d1ab19b0cc6d87ca7c44b058edf678bc3a3
> > Author: Thierry Reding <treding@nvidia.com>
> > Date: Tue Aug 15 15:41:10 2017 +0200
> >
> > drm/tegra: dc: Trace register accesses
> >
> > Add tracepoint events for display controller register accesses.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> >
> >
> > introduce the following compile 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)
>
> It looks as though this fails only for in-source builds, which is
> something I usually don't test. I'm working on a patch to fix this.
This should be fixed in today's linux-next by:
commit 702800b5d6f45b18db6b6d6b1057af6fd1c75e20
Author: Thierry Reding <treding@nvidia.com>
Date: Wed Aug 23 19:13:26 2017 +0200
drm/tegra: trace: Fix path to include
The TRACE_INCLUDE_FILE macro needs to specify the path relative to the
define_trace.h header rather than relative to the file defining it.
Reported-by: Dmitry Osipenko <digetx@gmail.com>
Tested-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-24 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:19 linux-next-20170823 failed to build for arm64/defconfig Shawn Lin
2017-08-23 8:53 ` Thierry Reding
2017-08-24 8:34 ` 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=20170824083451.GA25455@ulmo \
--to=treding@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawn.lin@rock-chips.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 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.