From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: add missing \n to UTS_RELEASE in the error_state
Date: Thu, 14 Feb 2013 10:02:12 +0000 [thread overview]
Message-ID: <20130214100212.GA2127@cantiga.alporthouse.com> (raw)
In-Reply-To: <1360833815-582-1-git-send-email-jani.nikula@intel.com>
On Thu, Feb 14, 2013 at 11:23:35AM +0200, Jani Nikula wrote:
> Amending
> commit 4518f611ba21ba165ea3714055938a8984a44ff9
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Wed Jan 23 16:16:35 2013 +0100
>
> drm/i915: dump UTS_RELEASE into the error_state
Perhaps mention which commit introduced UTS_RELEASE, though I thnk the
any stable conflict will be remarkably easy to resolve.
> CC: stable@vger.kernel.org
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
And I just got used to the enhanced PCI ID string.
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-02-14 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 9:23 [PATCH] drm/i915: add missing \n to UTS_RELEASE in the error_state Jani Nikula
2013-02-14 10:02 ` Chris Wilson [this message]
2013-02-14 12:27 ` [Intel-gfx] " 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=20130214100212.GA2127@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox