From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Zongyao Bai <zongyao.bai@intel.com>
Cc: igt-dev@lists.freedesktop.org, x.wang@intel.com
Subject: Re: [PATCH 1/5] fixup! tests/intel/xe_pat: limit number of dynamic tests
Date: Mon, 06 Apr 2026 15:42:28 -0700 [thread overview]
Message-ID: <87h5pnd82z.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20260406222703.3217769-2-zongyao.bai@intel.com>
On Mon, 06 Apr 2026 15:26:59 -0700, Zongyao Bai wrote:
>
About: "fixup! tests/intel/xe_pat: limit number of dynamic tests"
We don't rebase upstream branches so 'fixup!' doesn't make sense. Please
resend as regular patches (with a different title), when you send the next
version. You can add a 'Fixes :' tag (similar to kernel) if you want to
reference the previous patch being fixed. Thanks.
next prev parent reply other threads:[~2026-04-06 22:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 23:18 [PATCH 0/2] Randomize PAT test subset Zongyao Bai
2025-11-19 23:18 ` [PATCH 1/2] tests/intel/xe_pat: switch PAT tests to igt_srandom() Zongyao Bai
2025-11-20 15:46 ` Kamil Konieczny
2025-11-19 23:19 ` [PATCH 2/2] tests/intel/xe_pat: randomize PAT test subset for xe2 Zongyao Bai
2025-11-20 0:13 ` ✓ Xe.CI.BAT: success for Randomize PAT test subset Patchwork
2025-11-20 0:28 ` ✓ i915.CI.BAT: " Patchwork
2025-11-20 5:24 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-20 12:33 ` ✗ i915.CI.Full: " Patchwork
2026-04-06 22:26 ` [PATCH 0/5] " Zongyao Bai
2026-04-06 22:26 ` [PATCH 1/5] fixup! tests/intel/xe_pat: limit number of dynamic tests Zongyao Bai
2026-04-06 22:42 ` Dixit, Ashutosh [this message]
2026-04-06 22:53 ` Bai, Zongyao
2026-04-06 22:27 ` [PATCH 2/5] fixup! tests/xe: add some vm_bind pat_index tests Zongyao Bai
2026-04-06 22:27 ` [PATCH 3/5] tests/intel/xe_pat: cache and decode PAT entries Zongyao Bai
2026-04-06 22:27 ` [PATCH 4/5] tests/intel/xe_pat: detect wt support from cached " Zongyao Bai
2026-04-06 22:27 ` [PATCH 5/5] tests/intel/xe_pat: randomly generate test PAT set to cover more PAT index Zongyao Bai
2026-04-06 22:35 ` ✗ Fi.CI.BUILD: failure for Randomize PAT test subset (rev2) Patchwork
2026-04-06 23:15 ` [PATCH v3 0/5] Randomize PAT test subset Zongyao Bai
2026-04-06 23:15 ` [PATCH v3 1/5] tests/intel/xe_pat: fix typo in r2 wc debug print Zongyao Bai
2026-04-06 23:15 ` [PATCH v3 2/5] tests/intel/xe_pat: drop redundant manual srand initialization Zongyao Bai
2026-04-06 23:15 ` [PATCH v3 3/5] tests/intel/xe_pat: cache and decode PAT entries Zongyao Bai
2026-04-06 23:15 ` [PATCH v3 4/5] tests/intel/xe_pat: detect wt support from cached " Zongyao Bai
2026-04-06 23:15 ` [PATCH v3 5/5] tests/intel/xe_pat: randomly generate test PAT set to cover more PAT index Zongyao Bai
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=87h5pnd82z.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=x.wang@intel.com \
--cc=zongyao.bai@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.