All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, daniele.ceraolospurio@intel.com,
	lucas.demarchi@intel.com, thomas.hellstrom@linux.intel.com,
	rodrigo.vivi@intel.com
Subject: [PATCH 0/3] drm/xe: split PVC PCI ID commit to two
Date: Fri,  6 Sep 2024 15:06:01 +0300	[thread overview]
Message-ID: <cover.1725624296.git.jani.nikula@intel.com> (raw)

Split "drm/xe: Add PVC's PCI device IDs" in xe-for-CI into two, first
adding the PCI ID macros in drm-xe-next, and then using those macros in
xe-for-CI. It should be fine to add the PCI ID *macros* upstream, the
same as we're adding a ton of enabling for PVC. It's the identification
of the platform in xe_pci.c that couns, and that's split to xe-for-CI.

BR,
Jani.

Jani Nikula (1):
  [topic/xe-for-CI] Revert "drm/xe: Add PVC's PCI device IDs"

Rodrigo Vivi (2):
  drm/xe/pciids: Add PVC's PCI device ID macros
  drm/xe: Add PVC's PCI device IDs


-- 
2.39.2


             reply	other threads:[~2024-09-06 12:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 12:06 Jani Nikula [this message]
2024-09-06 12:06 ` [PATCH 1/3] [topic/xe-for-CI] Revert "drm/xe: Add PVC's PCI device IDs" Jani Nikula
2024-09-06 12:06 ` [PATCH 2/3] drm/xe/pciids: Add PVC's PCI device ID macros Jani Nikula
2024-09-06 15:59   ` Rodrigo Vivi
2024-09-19 11:55     ` Jani Nikula
2024-09-19 13:07       ` Lucas De Marchi
2024-09-23  9:37         ` Jani Nikula
2024-09-06 12:06 ` [PATCH 3/3] drm/xe: Add PVC's PCI device IDs Jani Nikula
2024-09-06 12:12 ` ✓ CI.Patch_applied: success for drm/xe: split PVC PCI ID commit to two Patchwork
2024-09-06 12:13 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-06 12:15 ` ✓ CI.KUnit: success " Patchwork
2024-09-06 12:27 ` ✓ CI.Build: " Patchwork
2024-09-06 12:29 ` ✓ CI.Hooks: " Patchwork
2024-09-06 12:30 ` ✓ CI.checksparse: " Patchwork
2024-09-06 13:09 ` ✓ CI.BAT: " 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=cover.1725624296.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.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.