From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>, Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3 v3] GTFIFODBG
Date: Sat, 11 Feb 2012 20:00:39 +0000 [thread overview]
Message-ID: <c55c5d$1ujrof@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120211162205.GC12283@phenom.ffwll.local>
On Sat, 11 Feb 2012 17:22:05 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Feb 09, 2012 at 10:15:17AM +0100, Ben Widawsky wrote:
> > Someday I will get simple patches in one version... Alas that day is not
> > today.
> >
> > Ben Widawsky (3):
> > drm/i915: use gtfifodbg
> > drm/i915: catch gtfifo errors on forcewake_put
> > drm/i915: check gtfifodbg after possibly failed writes
>
> I've slurped these three in for -next, thanks for the patches. There's a
> quibble though from your grumpy maintainer: Please keep a proper patch
> revision log in the commit message and don't just drop it randomly. In
> this case the r-b (v1) is pretty pointless because you don't say what
> you've changed (and that these patches aren't v1) ...
Daniel, can you add my reviewed-by to that series?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-11 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 9:15 [PATCH 0/3 v3] GTFIFODBG Ben Widawsky
2012-02-09 9:15 ` [PATCH 1/3] drm/i915: use gtfifodbg Ben Widawsky
2012-02-09 9:15 ` [PATCH 2/3] drm/i915: catch gtfifo errors on forcewake_put Ben Widawsky
2012-02-09 9:15 ` [PATCH 3/3] drm/i915: check gtfifodbg after possibly failed writes Ben Widawsky
2012-02-11 16:22 ` [PATCH 0/3 v3] GTFIFODBG Daniel Vetter
2012-02-11 20:00 ` Chris Wilson [this message]
2012-02-11 23:22 ` 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='c55c5d$1ujrof@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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.