From: Raag Jadav <raag.jadav@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Matt Atwood <matthew.s.atwood@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] drm/xe: remove unused xe_pciids.h harder, add missing PCI ID
Date: Thu, 9 Jan 2025 15:58:04 +0200 [thread overview]
Message-ID: <Z3_V7MHFINUqR6qs@black.fi.intel.com> (raw)
In-Reply-To: <20250109105032.2585416-1-jani.nikula@intel.com>
On Thu, Jan 09, 2025 at 12:50:32PM +0200, Jani Nikula wrote:
> Commit 493454445c95 ("drm/xe: switch to common PCI ID macros") removed
> xe_pciids.h via drm-intel-next. In the mean time, commit ae78ec0a52c4
> ("drm/xe/ptl: Add another PTL PCI ID") added to xe_pciids.h via
> drm-xe-next.
>
> The two commits were merged in commit 8f109f287fdc ("Merge drm/drm-next
> into drm-xe-next"), but xe_pciids.h wasn't removed, and the PCI ID
> wasn't added to pciids.h.
>
> Remove xe_pciids.h, and add the PCI ID to pciids.h.
Unless there's a nuance intended in the subject
s/harder/header
Raag
next prev parent reply other threads:[~2025-01-09 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 10:50 [PATCH] drm/xe: remove unused xe_pciids.h harder, add missing PCI ID Jani Nikula
2025-01-09 11:44 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2025-01-09 12:14 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-09 12:22 ` [PATCH] " Upadhyay, Tejas
2025-01-09 13:08 ` ✗ CI.Patch_applied: failure for " Patchwork
2025-01-09 13:58 ` Raag Jadav [this message]
2025-01-09 14:29 ` [PATCH] " Jani Nikula
2025-01-09 16:49 ` Matt Roper
2025-01-10 10:26 ` Jani Nikula
2025-01-12 3:26 ` ✗ i915.CI.Full: 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=Z3_V7MHFINUqR6qs@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
/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.