From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lee Shawn C <shawn.c.lee@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
Cooper Chiou <cooper.chiou@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/cml: Remove unsupport PCI ID
Date: Thu, 12 Dec 2019 22:29:46 +0200 [thread overview]
Message-ID: <20191212202946.GS1208@intel.com> (raw)
In-Reply-To: <20191210150415.10705-1-shawn.c.lee@intel.com>
On Tue, Dec 10, 2019 at 11:04:14PM +0800, Lee Shawn C wrote:
> commit 'a7b4deeb02b9 ("drm/i915/cml: Add CML PCI IDS)'
> introduced new PCI ID that CML support. But some PCI
> IDs were removed in BSpec for CML. This patch is used
> to eliminate the unsed ID.
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
> Cc: Cooper Chiou <cooper.chiou@intel.com>
> Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
Series pushed to dinq. Thanks.
> ---
> include/drm/i915_pciids.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> index 3e26a9178aaf..92873c3957c8 100644
> --- a/include/drm/i915_pciids.h
> +++ b/include/drm/i915_pciids.h
> @@ -448,9 +448,7 @@
> #define INTEL_CML_GT1_IDS(info) \
> INTEL_VGA_DEVICE(0x9B21, info), \
> INTEL_VGA_DEVICE(0x9BAA, info), \
> - INTEL_VGA_DEVICE(0x9BAB, info), \
> INTEL_VGA_DEVICE(0x9BAC, info), \
> - INTEL_VGA_DEVICE(0x9BA0, info), \
> INTEL_VGA_DEVICE(0x9BA5, info), \
> INTEL_VGA_DEVICE(0x9BA8, info), \
> INTEL_VGA_DEVICE(0x9BA4, info), \
> @@ -460,9 +458,7 @@
> #define INTEL_CML_GT2_IDS(info) \
> INTEL_VGA_DEVICE(0x9B41, info), \
> INTEL_VGA_DEVICE(0x9BCA, info), \
> - INTEL_VGA_DEVICE(0x9BCB, info), \
> INTEL_VGA_DEVICE(0x9BCC, info), \
> - INTEL_VGA_DEVICE(0x9BC0, info), \
> INTEL_VGA_DEVICE(0x9BC5, info), \
> INTEL_VGA_DEVICE(0x9BC8, info), \
> INTEL_VGA_DEVICE(0x9BC4, info), \
> --
> 2.17.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-12 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 15:04 [Intel-gfx] [PATCH] drm/i915/cml: Remove unsupport PCI ID Lee Shawn C
2019-12-10 8:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-12-10 8:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-10 9:24 ` Patchwork
2019-12-10 13:33 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2019-12-10 15:04 ` [Intel-gfx] [PATCH 2/2] drm/i915/cml: Separate U series pci id from origianl list Lee Shawn C
2019-12-12 20:29 ` Ville Syrjälä [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-25 20:24 [PATCH v2 1/2] commit 'a7b4deeb02b9 ("drm/i915/cml: Add CML PCI IDS)' introduced new PCI ID that CML support. But some sku is not support yet so remove them Lee Shawn C
2019-10-25 20:29 ` [Intel-gfx] [PATCH] drm/i915/cml: Remove unsupport PCI ID Lee Shawn C
2019-10-25 20:29 ` Lee Shawn C
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=20191212202946.GS1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=cooper.chiou@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=shawn.c.lee@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 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.