linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/pciids: switch to xe driver style PCI ID macros
Date: Wed, 22 May 2024 12:43:26 +0300	[thread overview]
Message-ID: <87ed9uqj0h.fsf@intel.com> (raw)
In-Reply-To: <87y184sm72.fsf@intel.com>

On Mon, 20 May 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 15 May 2024, Jani Nikula <jani.nikula@intel.com> wrote:
>> The PCI ID macros in xe_pciids.h allow passing in the macro to operate
>> on each PCI ID, making it more flexible. Convert i915_pciids.h to the
>> same pattern.
>>
>> INTEL_IVB_Q_IDS() for Quanta transcode remains a special case, and
>> unconditionally uses INTEL_QUANTA_VGA_DEVICE().
>>
>> Cc: Bjorn Helgaas <bhelgaas@google.com>
>> Cc: linux-pci@vger.kernel.org
>
> Bjorn, since I asked for acks on the last ones, I probably should here
> too. :)
>
> I'm hoping to stop mucking with the macros after this.

Okay, well, I pushed this to drm-intel-next, since this doesn't really
change x86 functionally, and you weren't all that interested the last
time. Hope it's fine. :)

BR,
Jani.


-- 
Jani Nikula, Intel

      reply	other threads:[~2024-05-22  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 16:56 [PATCH 1/2] drm/i915/pciids: switch to xe driver style PCI ID macros Jani Nikula
2024-05-16 13:25 ` Rodrigo Vivi
2024-05-20 12:27 ` Jani Nikula
2024-05-22  9:43   ` 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=87ed9uqj0h.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=bhelgaas@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).