All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"adam.miszczak@linux.intel.com" <adam.miszczak@linux.intel.com>
Subject: Re: [PATCH libdrm] intel: sync i915_pciids.h with kernel
Date: Thu, 20 Aug 2020 17:24:55 +0000	[thread overview]
Message-ID: <81f5cd962f8474c275fd7062b651e1ef28d40b66.camel@intel.com> (raw)
In-Reply-To: <20200820084642.26562-1-adam.miszczak@linux.intel.com>

On Thu, 2020-08-20 at 10:46 +0200, Adam Miszczak wrote:
> Add DG1 and clean-up VLV PCI IDs.
> 
> Align with kernel commits:
> f2bde2546b81 ("drm/i915: Remove dubious Valleyview PCI IDs")
> fd38cdb81105 ("drm/i915/dg1: Add DG1 PCI IDs")
> 

Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

But the current process for libdrm patches is to open a merge request in Freedesktop gitlab, when you do CC me.

> Signed-off-by: Adam Miszczak <
> adam.miszczak@linux.intel.com
> >
> Cc: José Roberto de Souza <
> jose.souza@intel.com
> >
> ---
>  intel/i915_pciids.h | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/intel/i915_pciids.h b/intel/i915_pciids.h
> index d6cb2899..8e7ae30e 100644
> --- a/intel/i915_pciids.h
> +++ b/intel/i915_pciids.h
> @@ -258,9 +258,7 @@
>  	INTEL_VGA_DEVICE(0x0f30, info), \
>  	INTEL_VGA_DEVICE(0x0f31, info), \
>  	INTEL_VGA_DEVICE(0x0f32, info), \
> -	INTEL_VGA_DEVICE(0x0f33, info), \
> -	INTEL_VGA_DEVICE(0x0157, info), \
> -	INTEL_VGA_DEVICE(0x0155, info)
> +	INTEL_VGA_DEVICE(0x0f33, info)
>  
>  #define INTEL_BDW_ULT_GT1_IDS(info) \
>  	INTEL_VGA_DEVICE(0x1606, info), /* GT1 ULT */ \
> @@ -618,4 +616,8 @@
>  	INTEL_VGA_DEVICE(0x4C90, info), \
>  	INTEL_VGA_DEVICE(0x4C9A, info)
>  
> +/* DG1 */
> +#define INTEL_DG1_IDS(info) \
> +	INTEL_VGA_DEVICE(0x4905, info)
> +
>  #endif /* _I915_PCIIDS_H */
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-08-20 17:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  8:46 [PATCH libdrm] intel: sync i915_pciids.h with kernel Adam Miszczak
2020-08-20 17:24 ` Souza, Jose [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-16 12:37 ramadevi.gandi
2020-03-20  0:38 Swathi Dhanavanthri
2020-03-23 12:04 ` Timo Aaltonen
2019-12-10 20:06 José Roberto de Souza
2019-12-12 17:17 ` Matt Roper
2019-12-16 16:52   ` Souza, Jose
2019-08-30 20:32 Anusha Srivatsa
2019-09-05 17:54 ` Souza, Jose
2019-03-22 20:35 Anusha
2019-03-22 21:03 ` Souza, Jose
2019-03-25 10:28   ` Jani Nikula
2019-03-21 17:58 Anusha
2019-03-21 22:04 ` Souza, Jose
2019-02-02  8:07 Rodrigo Vivi
2019-02-04 18:19 ` Lionel Landwerlin

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=81f5cd962f8474c275fd7062b651e1ef28d40b66.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=dri-devel@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 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.