From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "Vivekanandan,
Balasubramani" <balasubramani.vivekanandan@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [igt-dev] [Intel-xe] [PATCH igt 1/4] lib: Add xe_pciids.h
Date: Fri, 1 Sep 2023 12:17:53 +0000 [thread overview]
Message-ID: <4fa2fbf667feb0a47fc7063171a3661d2c12082a.camel@intel.com> (raw)
In-Reply-To: <73mgfju4usrlbao3ejqf36joimrp722pgnydmxarf6hvg5gu5s@no2ox2hlqgpj>
On Fri, 2023-09-01 at 02:21 -0700, Lucas De Marchi wrote:
> +Rodrigo
>
> On Thu, Aug 31, 2023 at 11:58:23AM +0530, Balasubramani Vivekanandan
> wrote:
> > On 29.08.2023 07:11, Lucas De Marchi wrote:
> > > With the introduction of Lunar Lake, igt won't be able to just
> > > re-use
> > > i915_pciids.h for both drivers anymore since the support for LNL
> > > is only
> > > coming with the xe module. Copy xe_pciids.h from the drm-xe-next
> > > branch
> > > (up to commit b9c9020fc816 ("drm/xe/pvc: Use fast copy engines as
> > > migrate engine on PVC") and start including it where needed. This
> > > brings
> > > all the LNL PCI IDs.
> >
> > I couldn't find the commit hash b9c9020fc816. Is it lost due to
> > rebase?
> > In that case, does it make sense to use the commit hash or just
> > keep the
> > commit subject?
>
> Rodrigo, did you tag the branch before force pushing? If so, can you
> push a tag like the archive/* ones? This would allow people to see
> the
> commit referenced, even if later we force push the branch.
ops, sorry for that.
The tag is there now:
drm-xe-next-2023-08-29
btw, I noticed we are using 2 different styles, should we always add
'archive/' or should we drop that?
Is there any tag that is not an archive?
>
>
> Lucas De Marchi
next prev parent reply other threads:[~2023-09-01 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 14:11 [igt-dev] [PATCH igt 0/4] Add LNL support to xe tests Lucas De Marchi
2023-08-29 14:11 ` [igt-dev] [PATCH igt 1/4] lib: Add xe_pciids.h Lucas De Marchi
2023-08-31 6:28 ` [igt-dev] [Intel-xe] " Balasubramani Vivekanandan
2023-08-31 6:55 ` Balasubramani Vivekanandan
2023-09-01 9:21 ` Lucas De Marchi
2023-09-01 12:17 ` Vivi, Rodrigo [this message]
2023-08-29 14:11 ` [igt-dev] [PATCH igt 2/4] lib/intel_chipset: Add Lunar Lake support Lucas De Marchi
2023-08-31 6:48 ` [igt-dev] [Intel-xe] " Balasubramani Vivekanandan
2023-08-31 6:51 ` Balasubramani Vivekanandan
2023-08-31 17:15 ` Matt Roper
2023-08-29 14:11 ` [igt-dev] [PATCH igt 3/4] lib/intel_device_info: Add blitter cmd info for Lunar Lake Lucas De Marchi
2023-08-30 23:48 ` Srivatsa, Anusha
2023-08-29 14:11 ` [igt-dev] [PATCH igt 4/4] tests/xe_debugfs: skip page table level check for Xe2 Lucas De Marchi
2023-08-30 23:50 ` Srivatsa, Anusha
2023-08-29 14:26 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add LNL support to xe tests Patchwork
2023-08-29 14:59 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-29 15:26 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-08-29 21:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-30 21:07 ` [igt-dev] [Intel-xe] [PATCH igt 0/4] " Rodrigo Vivi
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=4fa2fbf667feb0a47fc7063171a3661d2c12082a.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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