public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Removing PCI IDs that are no	longer listed as Kabylake.
Date: Wed, 29 Jun 2016 16:08:35 +0000	[thread overview]
Message-ID: <1467216469.1933.249.camel@intel.com> (raw)
In-Reply-To: <871t3gs5yr.fsf@intel.com>

On Wed, 2016-06-29 at 12:24 +0300, Jani Nikula wrote:
> On Fri, 24 Jun 2016, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > 
> > This is unusual. Usually IDs listed on early stages of platform
> > definition are kept there as reserved for later use.
> > 
> > However these IDs here are not listed anymore in any of steppings
> > and devices IDs tables for Kabylake on configurations overview
> > section of BSpec.
> > 
> > So it is better removing them before they become used in any
> > other future platform.
> > 
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Please reply to the list when you actually push.

ops. I merged yesterday but forgot to reply, sorry.

> 
> Both of these could have used cc: drm-intel-fixes because we support
> kbl
> starting v4.7. I've picked them to fixes now.

Thanks

> 
> BR,
> Jani.
> 
> > 
> > ---
> >  include/drm/i915_pciids.h | 9 ++-------
> >  1 file changed, 2 insertions(+), 7 deletions(-)
> > 
> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> > index 87dde1c..33466bf 100644
> > --- a/include/drm/i915_pciids.h
> > +++ b/include/drm/i915_pciids.h
> > @@ -325,15 +325,10 @@
> >  #define INTEL_KBL_GT3_IDS(info) \
> >  	INTEL_VGA_DEVICE(0x5923, info), /* ULT GT3 */ \
> >  	INTEL_VGA_DEVICE(0x5926, info), /* ULT GT3 */ \
> > -	INTEL_VGA_DEVICE(0x5927, info), /* ULT GT3 */ \
> > -	INTEL_VGA_DEVICE(0x592B, info), /* Halo GT3 */ \
> > -	INTEL_VGA_DEVICE(0x592A, info) /* SRV GT3 */
> > +	INTEL_VGA_DEVICE(0x5927, info) /* ULT GT3 */
> >  
> >  #define INTEL_KBL_GT4_IDS(info) \
> > -	INTEL_VGA_DEVICE(0x5932, info), /* DT  GT4 */ \
> > -	INTEL_VGA_DEVICE(0x593B, info), /* Halo GT4 */ \
> > -	INTEL_VGA_DEVICE(0x593A, info), /* SRV GT4 */ \
> > -	INTEL_VGA_DEVICE(0x593D, info)  /* WKS GT4 */
> > +	INTEL_VGA_DEVICE(0x593B, info) /* Halo GT4 */
> >  
> >  #define INTEL_KBL_IDS(info) \
> >  	INTEL_KBL_GT1_IDS(info), \
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

  reply	other threads:[~2016-06-29 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 21:50 [PATCH 1/2] drm/i915: Add more Kabylake PCI IDs Rodrigo Vivi
2016-06-23 21:50 ` [PATCH 2/2] drm/i915: Removing PCI IDs that are no longer listed as Kabylake Rodrigo Vivi
2016-06-28 21:40   ` Pandiyan, Dhinakaran
2016-06-29  9:24   ` [Intel-gfx] " Jani Nikula
2016-06-29 16:08     ` Vivi, Rodrigo [this message]
2016-06-24 10:11 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] drm/i915: Add more Kabylake PCI IDs Patchwork
2016-06-24 22:06 ` [PATCH 1/2] " Pandiyan, Dhinakaran
2016-06-24 22:31   ` Pandiyan, Dhinakaran

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=1467216469.1933.249.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=mesa-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox