From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"nirmoy.das@linux.intel.com" <nirmoy.das@linux.intel.com>
Cc: "everestkc@everestkc.com.np" <everestkc@everestkc.com.np>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v1 1/1] drm/xe/guc: Fix missing init value and add register order check
Date: Thu, 31 Oct 2024 10:22:31 -0400 [thread overview]
Message-ID: <c1512553-eed1-4673-aa82-3430efafc50d@intel.com> (raw)
In-Reply-To: <6894f0472669600c06d43457bf2be60e26892ebb.camel@intel.com>
CI test rerun on the 139890 and result is good. Sounds like we don't
need to worry about that patch.
Now we can go through normal review process.
Regards,
Zhanjun Dong
On 2024-10-24 7:50 p.m., Teres Alexis, Alan Previn wrote:
> On Thu, 2024-10-24 at 14:13 +0000, Dong, Zhanjun wrote:
>> Yes, I will send next revision in a series, which include that patch.
>>
>> Regards,
>> Zhanjun
>
> alan: I just noticed the other patch DID get sent to Xe?
> (https://patchwork.freedesktop.org/series/139890/) but CI results was
> only there for rev4 - nothing on rev4-resend. Wondering if Nirmoy
> wanted you to go ahead and create a two-patch series with the Everest's
> patch followed and your patch that adds the lower-vs-higher-dword
> enforcement.
next prev parent reply other threads:[~2024-10-31 14:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 19:23 [PATCH v1 1/1] drm/xe/guc: Fix missing init value and add register order check Zhanjun Dong
2024-10-24 11:09 ` ✓ CI.Patch_applied: success for series starting with [v1,1/1] " Patchwork
2024-10-24 11:09 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 11:10 ` ✓ CI.KUnit: " Patchwork
2024-10-24 11:22 ` ✓ CI.Build: " Patchwork
2024-10-24 11:24 ` ✓ CI.Hooks: " Patchwork
2024-10-24 11:26 ` ✓ CI.checksparse: " Patchwork
2024-10-24 11:27 ` [PATCH v1 1/1] " Nirmoy Das
2024-10-24 14:13 ` Dong, Zhanjun
2024-10-24 23:50 ` Teres Alexis, Alan Previn
2024-10-31 14:22 ` Dong, Zhanjun [this message]
2024-10-31 16:55 ` Dong, Zhanjun
2024-10-24 11:47 ` ✗ CI.BAT: failure for series starting with [v1,1/1] " Patchwork
2024-10-25 6:27 ` ✓ CI.FULL: success " Patchwork
2024-10-29 0:00 ` ✓ CI.Patch_applied: success for series starting with [v1,1/1] drm/xe/guc: Fix missing init value and add register order check (rev2) Patchwork
2024-10-29 0:01 ` ✓ CI.checkpatch: " Patchwork
2024-10-29 0:02 ` ✓ CI.KUnit: " Patchwork
2024-10-29 0:13 ` ✓ CI.Build: " Patchwork
2024-10-29 0:16 ` ✓ CI.Hooks: " Patchwork
2024-10-29 0:17 ` ✓ CI.checksparse: " Patchwork
2024-10-29 0:40 ` ✗ CI.BAT: failure " Patchwork
2024-10-29 1:39 ` ✗ CI.FULL: " Patchwork
2024-10-31 22:38 ` [PATCH v1 1/1] drm/xe/guc: Fix missing init value and add register order check Teres Alexis, Alan Previn
2024-11-01 14:43 ` Dong, Zhanjun
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=c1512553-eed1-4673-aa82-3430efafc50d@intel.com \
--to=zhanjun.dong@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=everestkc@everestkc.com.np \
--cc=intel-xe@lists.freedesktop.org \
--cc=nirmoy.das@linux.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