From: Jani Nikula <jani.nikula@intel.com>
To: Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: clinton.a.taylor@intel.com, kamil.konieczny@linux.intel.com,
zbigniew.kempczynski@intel.com,
Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>
Subject: Re: [PATCH v2] lib: sync PCI ID macros with kernel
Date: Fri, 08 Nov 2024 12:20:44 +0200 [thread overview]
Message-ID: <874j4if2mb.fsf@intel.com> (raw)
In-Reply-To: <20241107231457.70157-1-ngai-mint.kwan@linux.intel.com>
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
some old cruft in there.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-08 10:20 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 ` Jani Nikula [this message]
2024-11-08 15:46 ` [PATCH v2] lib: sync PCI ID macros with kernel Lucas De Marchi
2024-11-11 9:07 ` Jani Nikula
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=874j4if2mb.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox