From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org
Subject: [ANNOUNCE] 3.8.10-rt6
Date: Mon, 29 Apr 2013 22:12:02 +0200 [thread overview]
Message-ID: <20130429201202.GB7979@linutronix.de> (raw)
Dear RT Folks,
I'm pleased to announce the 3.8.10-rt6 release.
changes since v3.8.10-rt5:
- the i915 compiles again after I broke it in the last release. A patch
was sent by Carsten Emde.
Known issues:
- SLxB is broken on PowerPC.
- suspend / resume seems to program program the timer wrong and wait
ages until it continues.
The delta patch against v3.8.10-rt5 is appended below and can be found here:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/incr/patch-3.8.10-rt5-rt6.patch.xz
The RT patch against 3.8.9 can be found here:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/patch-3.8.10-rt6.patch.xz
The split quilt queue is available at:
https://www.kernel.org/pub/linux/kernel/projects/rt/3.8/patches-3.8.10-rt6.tar.xz
Sebastian
diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
index 81125de..eabd3dd 100644
--- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
+++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
@@ -814,6 +814,7 @@ i915_gem_do_execbuffer(struct drm_device *dev, void *data,
struct intel_ring_buffer *ring;
u32 ctx_id = i915_execbuffer2_get_context_id(*args);
u32 exec_start, exec_len;
+ u32 seqno;
u32 mask;
u32 flags;
int ret, mode, i;
@@ -1068,7 +1069,8 @@ i915_gem_do_execbuffer(struct drm_device *dev, void *data,
goto err;
}
- trace_i915_gem_ring_dispatch(ring, intel_ring_get_seqno(ring), flags);
+ seqno = intel_ring_get_seqno(ring);
+ trace_i915_gem_ring_dispatch(ring, seqno, flags);
i915_trace_irq_get(ring, seqno);
i915_gem_execbuffer_move_to_active(&objects, ring);
diff --git a/localversion-rt b/localversion-rt
index 0efe7ba..8fc605d 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
--rt5
+-rt6
next reply other threads:[~2013-04-29 20:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 20:12 Sebastian Andrzej Siewior [this message]
2013-04-29 21:19 ` [ANNOUNCE] 3.8.10-rt6 Clark Williams
2013-04-30 8:47 ` John Kacur
2013-04-30 10:35 ` Sebastian Andrzej Siewior
2013-04-30 17:09 ` Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6) Sebastian Andrzej Siewior
2013-04-30 18:08 ` Steven Rostedt
2013-05-03 9:59 ` Sebastian Andrzej Siewior
2013-05-03 15:31 ` Steven Rostedt
2013-04-30 19:18 ` Clark Williams
2013-04-30 21:54 ` Clark Williams
2013-04-30 22:31 ` Borislav Petkov
2013-05-02 7:59 ` Sebastian Andrzej Siewior
2013-05-01 8:30 ` Bernhard Schiffner
2013-05-01 8:32 ` Bernhard Schiffner
2013-05-03 10:27 ` Sebastian Andrzej Siewior
2013-05-03 17:46 ` Bernhard Schiffner
[not found] ` <23187402.mkEEi1N7Lp@bs8>
2013-04-30 7:26 ` [ANNOUNCE] 3.8.10-rt6 Sebastian Andrzej Siewior
2013-05-03 4:40 ` Jain Priyanka-B32167
2013-05-03 8:40 ` Sebastian Andrzej Siewior
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=20130429201202.GB7979@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).