From: Steven Rostedt <rostedt@goodmis.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>, Jiri Pirko <jiri@resnulli.us>
Subject: Re: linux-next: Tree for Jul 13 (net/core/devlink with Tracing)
Date: Wed, 13 Jul 2016 15:42:20 -0400 [thread overview]
Message-ID: <20160713154220.75b3896a@gandalf.local.home> (raw)
In-Reply-To: <e2a29ece-79cb-6892-2e53-0b05d4ef781d@infradead.org>
On Wed, 13 Jul 2016 08:12:16 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 07/12/16 23:47, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20160712:
> >
>
> on x86_64:
> (full randconfig file is attached)
>
>
> CC net/core/devlink.o
> In file included from ../include/trace/define_trace.h:95:0,
> from ../include/trace/events/devlink.h:51,
> from ../net/core/devlink.c:30:
> ../include/trace/events/devlink.h: In function 'trace_event_get_offsets_devlink_hwmsg':
> ../include/trace/events/devlink.h:25:51: error: dereferencing pointer to incomplete type
> __string(owner_name, devlink->dev->driver->owner->name)
[snip the rest]
When I remove all references to the owner_name (and that crazy
dereferencing above), it compiles fine. There must be something funky
with that devlink->dev->driver->owner->name part.
-- Steve
prev parent reply other threads:[~2016-07-13 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 6:47 linux-next: Tree for Jul 13 Stephen Rothwell
2016-07-13 15:12 ` linux-next: Tree for Jul 13 (net/core/devlink with Tracing) Randy Dunlap
2016-07-13 19:42 ` Steven Rostedt [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=20160713154220.75b3896a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).