public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Anuj Phogat <anuj.phogat@gmail.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] i915_pciids: Change a KBL pci id to	GT2 from GT1.5
Date: Fri, 22 Sep 2017 14:23:34 +0300	[thread overview]
Message-ID: <878th7t1s9.fsf@intel.com> (raw)
In-Reply-To: <87efqzt2jo.fsf@intel.com>

On Fri, 22 Sep 2017, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Fri, 22 Sep 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>> On Thu, Sep 21, 2017 at 10:03:48PM +0000, Anuj Phogat wrote:
>>> On Thu, Sep 21, 2017 at 2:58 PM, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>>> > In sync with 41693fd52373 ("drm/i915/kbl: Change a KBL pci id
>>> > to GT2 from GT1.5")
>>> >
>>> > "See Mesa commit 9c588ff"
>>> >
>>> > Cc: Anuj Phogat <anuj.phogat@gmail.com>
>>> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> > ---
>>> >  lib/i915_pciids.h | 2 +-
>>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>>> >
>>> > diff --git a/lib/i915_pciids.h b/lib/i915_pciids.h
>>> > index 3e4f9614..0d2b125c 100644
>>> > --- a/lib/i915_pciids.h
>>> > +++ b/lib/i915_pciids.h
>>> > @@ -303,7 +303,6 @@
>>> >  #define INTEL_KBL_GT1_IDS(info)        \
>>> >         INTEL_VGA_DEVICE(0x5913, info), /* ULT GT1.5 */ \
>>> >         INTEL_VGA_DEVICE(0x5915, info), /* ULX GT1.5 */ \
>>> > -       INTEL_VGA_DEVICE(0x5917, info), /* DT  GT1.5 */ \
>>> >         INTEL_VGA_DEVICE(0x5906, info), /* ULT GT1 */ \
>>> >         INTEL_VGA_DEVICE(0x590E, info), /* ULX GT1 */ \
>>> >         INTEL_VGA_DEVICE(0x5902, info), /* DT  GT1 */ \
>>> > @@ -313,6 +312,7 @@
>>> >
>>> >  #define INTEL_KBL_GT2_IDS(info)        \
>>> >         INTEL_VGA_DEVICE(0x5916, info), /* ULT GT2 */ \
>>> > +       INTEL_VGA_DEVICE(0x5917, info), /* DT  GT2 */   \
>>> Mobile GT2
>>> >         INTEL_VGA_DEVICE(0x5921, info), /* ULT GT2F */ \
>>> >         INTEL_VGA_DEVICE(0x591E, info), /* ULX GT2 */ \
>>> >         INTEL_VGA_DEVICE(0x5912, info), /* DT  GT2 */ \
>>> > --
>>> > 2.13.5
>>> >
>>> With above change:
>>> Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
>>
>> Fixed and merged.
>> Thanks for starting this and for the review.
>
> Should it have been Cc: stable? Fixes:?

...was the kernel patch...?

J.

>
> BR,
> Jani.
>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-09-22 11:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 21:58 [PATCH i-g-t] i915_pciids: Change a KBL pci id to GT2 from GT1.5 Rodrigo Vivi
2017-09-21 22:03 ` Anuj Phogat
2017-09-21 22:43   ` Rodrigo Vivi
2017-09-22 11:07     ` Jani Nikula
2017-09-22 11:23       ` Jani Nikula [this message]
2017-09-22 12:47         ` Rodrigo Vivi
2017-09-22 11:47 ` ✗ Fi.CI.BAT: failure for " Patchwork

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=878th7t1s9.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=anuj.phogat@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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