From: Chad Versace <chad.versace@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2 libdrm] intel: Fix Haswell GT3 names.
Date: Tue, 14 May 2013 13:58:02 -0700 [thread overview]
Message-ID: <5192A55A.7020302@linux.intel.com> (raw)
In-Reply-To: <1368478120-22036-1-git-send-email-rodrigo.vivi@gmail.com>
On 05/13/2013 01:48 PM, Rodrigo Vivi wrote:
> When publishing first HSW ids we weren't allowed to use "GT3" codname.
> But this is the correct codname and Mesa is using it already.
> So to avoid people getting confused why in Mesa it is called GT3 and here
> it is called GT2_PLUS let's fix this name in a standard and correct way.
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> ---
> intel/intel_chipset.h | 53 ++++++++++++++++++++++++++-------------------------
> 1 file changed, 27 insertions(+), 26 deletions(-)
For patch 1,
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
prev parent reply other threads:[~2013-05-14 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:48 [PATCH 1/2 libdrm] intel: Fix Haswell GT3 names Rodrigo Vivi
2013-05-13 20:48 ` [PATCH 2/2 libdrm] intel: Adding more reserved PCI IDs for Haswell Rodrigo Vivi
2013-05-14 20:58 ` Chad Versace [this message]
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=5192A55A.7020302@linux.intel.com \
--to=chad.versace@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
/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