From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>
Cc: Matt Atwood <matthew.s.atwood@intel.com>,
intel-xe@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe/ptl: Add another PTL PCI ID
Date: Mon, 25 Nov 2024 11:09:31 +0200 [thread overview]
Message-ID: <87zflny910.fsf@intel.com> (raw)
In-Reply-To: <20241122230404.GH4891@mdroper-desk1.amr.corp.intel.com>
On Fri, 22 Nov 2024, Matt Roper <matthew.d.roper@intel.com> wrote:
> Applied to drm-xe-next (and the referenced GuC patch has also already
> landed earlier today).
>
> Since drm-xe-next hasn't had a backmerge yet to pick up the conversion
> of xe_pciids.h -> pciids.h I had to 'dim cat-to-fixup' to get the change
> to stick around in pciids.h when drm-tip gets re-generated. Although
> the old xe_pciids.h header also seems to be coming back now and I
> couldn't get the fixup patch to delete it properly. Presumably that
> will clear itself up whenever a backmerge happens, but +Cc Lucas FYI.
In general, please talk to the maintainers *before* doing stuff like
this, not after.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-11-25 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 23:44 [PATCH] drm/xe/ptl: Add another PTL PCI ID Matt Atwood
2024-11-15 0:25 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-15 0:25 ` ✓ CI.checkpatch: " Patchwork
2024-11-15 0:26 ` ✓ CI.KUnit: " Patchwork
2024-11-15 0:38 ` ✓ CI.Build: " Patchwork
2024-11-15 0:40 ` ✓ CI.Hooks: " Patchwork
2024-11-15 0:41 ` ✗ CI.checksparse: warning " Patchwork
2024-11-15 1:10 ` ✓ CI.BAT: success " Patchwork
2024-11-15 18:48 ` ✗ CI.FULL: failure " Patchwork
2024-11-19 9:21 ` [PATCH] " Jordan Justen
2024-11-22 23:18 ` Matt Roper
2024-11-25 9:09 ` Jani Nikula [this message]
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=87zflny910.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jordan.l.justen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@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.