From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>,
igt-dev@lists.freedesktop.org, clinton.a.taylor@intel.com,
kamil.konieczny@linux.intel.com, zbigniew.kempczynski@intel.com
Subject: Re: [PATCH v2] lib: sync PCI ID macros with kernel
Date: Mon, 11 Nov 2024 11:07:39 +0200 [thread overview]
Message-ID: <87wmhacf50.fsf@intel.com> (raw)
In-Reply-To: <lkiuylps7ka6qbno3gjtpkjbvu6dxpbkjw6725cri35coysxcz@yfcafnu4oguh>
On Fri, 08 Nov 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Nov 08, 2024 at 12:20:44PM +0200, Jani Nikula wrote:
>>On Thu, 07 Nov 2024, Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com> wrote:
>>> diff --git a/lib/i915/perf.c b/lib/i915/perf.c
>>> index ef2f74be8..9eb1141d4 100644
>>> --- a/lib/i915/perf.c
>>> +++ b/lib/i915/perf.c
>>> @@ -37,7 +37,7 @@
>>>
>>> #include <i915_drm.h>
>>>
>>> -#include "i915_pciids.h"
>>> +#include "pciids.h"
>>> #include "i915_pciids_local.h"
>>
>>After this gets merged, maybe you could write a follow-up patch that
>>renames i915_pciids_local.h to pciids_local.h and cleans it up; there's
>
> Actually to remove it. Why are we still carrying that?
To cater for igt perf code, which uses smaller granularity than the
kernel. It's a good question whether we should split the macros up
further in kernel for the needs of perf.
> Or maybe keep it just for the IDs from the topic branch (which we won't
> add more to, hopefully) so we can keep sync'ing with drm-xe, or
> drm-intel or drm-next, depending on the context.
There no more PCI IDs in the topic branches, even PVC IDs are now in
-next, but we just enable those PCI IDs in the topic branch.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-11 9:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 23:14 [PATCH v2] lib: sync PCI ID macros with kernel Ngai-Mint Kwan
2024-11-08 0:21 ` ✓ Fi.CI.BAT: success for lib: sync PCI ID macros with kernel (rev2) Patchwork
2024-11-08 0:22 ` ✓ CI.xeBAT: " Patchwork
2024-11-08 3:58 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-08 10:20 ` [PATCH v2] lib: sync PCI ID macros with kernel Jani Nikula
2024-11-08 15:46 ` Lucas De Marchi
2024-11-11 9:07 ` Jani Nikula [this message]
2024-11-13 14:13 ` Kamil Konieczny
2024-11-13 14:36 ` Lucas De Marchi
2024-11-14 9:45 ` Jani Nikula
2024-11-08 14:49 ` Kamil Konieczny
2024-11-08 15:50 ` Lucas De Marchi
2024-11-08 17:51 ` Ngai-Mint Kwan
2024-11-08 21:11 ` Kamil Konieczny
2024-11-09 8:07 ` ✗ CI.xeFULL: failure for lib: sync PCI ID macros with kernel (rev2) 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=87wmhacf50.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=ngai-mint.kwan@linux.intel.com \
--cc=zbigniew.kempczynski@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.