[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140319015415.GD7956@bwidawsk.net>
Date: Tue, 18 Mar 2014 18:54:15 -0700
From: Ben Widawsky <ben@...dawsk.net>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Daniel Vetter <daniel.vetter@...ll.ch>,
intel-gfx@...ts.freedesktop.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [Intel-gfx] linux-next: build failure after merge of the
drm-intel tree
On Tue, Mar 18, 2014 at 09:18:42PM -0400, Steven Rostedt wrote:
> On Wed, 19 Mar 2014 11:53:50 +1100
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
>
> > Caused by commit a25ca17c1eac ("drm/i915: Do not dereference pointers
> > from ring buffer in evict event").
> >
> > I have used the drm-intel tree from next-20140318 for today.
> >
>
> Bah! I'm still suffering from jet lag (just came back from Linux-Tage
> in Chemnitz).
>
> The next time I compile test a patch for a module, I'll make sure I have
> that module's config option set :-( The woe of using localmodconfig. I
> should have picked the box with the i915. :-/
>
> Below is the fix. I'll repost a v2 of the original patch.
>
> Sorry about that.
>
I was about to send out the same fix when I saw this.
Reviewed-by: Ben Widawsky <ben@...dawsk.net>
> -- Steve
>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index f3e8a90..783ae08 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -243,7 +243,7 @@ TRACE_EVENT(i915_gem_evict_vm,
> ),
>
> TP_fast_assign(
> - __entry->dev = dev->primary->index;
> + __entry->dev = vm->dev->primary->index;
> __entry->vm = vm;
> ),
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@...ts.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ben Widawsky, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists