All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	<intel-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the drm-intel tree
Date: Tue, 18 Mar 2014 21:18:42 -0400	[thread overview]
Message-ID: <20140318211842.017be730@gandalf.local.home> (raw)
In-Reply-To: <20140319115350.7860f102a804a9975ba6e93d@canb.auug.org.au>

On Wed, 19 Mar 2014 11:53:50 +1100
Stephen Rothwell <sfr@canb.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.

-- 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;
 			  ),
 

WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: linux-next: build failure after merge of the drm-intel tree
Date: Tue, 18 Mar 2014 21:18:42 -0400	[thread overview]
Message-ID: <20140318211842.017be730@gandalf.local.home> (raw)
In-Reply-To: <20140319115350.7860f102a804a9975ba6e93d@canb.auug.org.au>

On Wed, 19 Mar 2014 11:53:50 +1100
Stephen Rothwell <sfr@canb.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.

-- 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;
 			  ),

  reply	other threads:[~2014-03-19  1:18 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  0:53 linux-next: build failure after merge of the drm-intel tree Stephen Rothwell
2014-03-19  0:53 ` Stephen Rothwell
2014-03-19  1:18 ` Steven Rostedt [this message]
2014-03-19  1:18   ` Steven Rostedt
2014-03-19  1:54   ` [Intel-gfx] " Ben Widawsky
2014-03-19  1:54     ` Ben Widawsky
2014-03-19  7:20     ` Daniel Vetter
2014-03-19  7:20       ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2022-08-26  2:36 Stephen Rothwell
2022-08-26  2:36 ` Stephen Rothwell
2022-08-26  7:50 ` Jani Nikula
2022-08-26  7:50   ` Jani Nikula
2022-04-26  2:08 Stephen Rothwell
2022-04-26  2:08 ` Stephen Rothwell
2022-04-26  7:36 ` Jani Nikula
2022-04-26  7:36   ` Jani Nikula
2022-02-15  1:10 Stephen Rothwell
2022-02-15  1:10 ` Stephen Rothwell
2022-02-15 12:11 ` Jani Nikula
2022-02-15 12:11   ` Jani Nikula
2021-05-21  1:58 Stephen Rothwell
2021-05-21  1:58 ` Stephen Rothwell
2021-01-19 23:57 Stephen Rothwell
2021-01-19 23:57 ` Stephen Rothwell
2021-01-21  1:11 ` Stephen Rothwell
2021-01-21  1:11   ` Stephen Rothwell
2019-12-09 22:39 Stephen Rothwell
2019-12-09 22:42 ` Stephen Rothwell
2019-12-11  9:31   ` Jani Nikula
2019-12-11  9:31     ` Jani Nikula
2019-03-27  2:59 Stephen Rothwell
2019-03-27  2:59 ` Stephen Rothwell
2019-03-27 11:07 ` Joonas Lahtinen
2019-03-27 11:07   ` Joonas Lahtinen
2019-03-27 11:31   ` Stephen Rothwell
2019-03-27 11:31     ` Stephen Rothwell
2018-07-13  1:54 Stephen Rothwell
2018-07-23  2:29 ` Stephen Rothwell
2018-05-08  1:07 Stephen Rothwell
2018-05-08  7:08 ` Oleksandr Andrushchenko
2018-05-08  7:08   ` Oleksandr Andrushchenko
2018-05-09  5:02 ` Stephen Rothwell
2018-05-09  5:02   ` Stephen Rothwell
2018-05-09  5:08   ` Christoph Hellwig
2018-05-09  5:18     ` Stephen Rothwell
2016-10-17 23:59 Stephen Rothwell
2016-10-18  6:26 ` Daniel Vetter
2016-08-23  1:56 Stephen Rothwell
2016-08-23  1:56 ` Stephen Rothwell
2016-08-23 16:33 ` Daniel Vetter
2016-08-23 16:33   ` Daniel Vetter
2016-05-23  2:24 Stephen Rothwell
2016-05-23  2:24 ` Stephen Rothwell
2014-04-03  1:24 Stephen Rothwell
2014-04-03  1:24 ` Stephen Rothwell
2013-02-15  2:37 Stephen Rothwell
2013-02-15  2:37 ` Stephen Rothwell
2013-02-15  9:30 ` Daniel Vetter
2013-02-15  9:30   ` Daniel Vetter
2013-02-15 16:16   ` Jesse Barnes
2013-02-19  2:01     ` Stephen Rothwell
2013-02-19 10:28       ` Daniel Vetter

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=20140318211842.017be730@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.