From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Lis, Tomasz" <tomasz.lis@intel.com>, intel-xe@lists.freedesktop.org
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>
Subject: Re: [PATCH v8 1/4] drm/xe/vf: Divide GGTT ballooning into allocation and insertion
Date: Fri, 11 Apr 2025 18:32:48 +0200 [thread overview]
Message-ID: <6394d86d-9daf-4955-9262-8c6a83b996c6@intel.com> (raw)
In-Reply-To: <8de5029e-cffc-4973-9c62-ff3683d38c9a@intel.com>
On 11.04.2025 16:35, Lis, Tomasz wrote:
>
> On 10.04.2025 18:54, Michal Wajdeczko wrote:
>> On 09.04.2025 23:13, Tomasz Lis wrote:
...
>>>
>>> diff --git a/drivers/gpu/drm/xe/xe_ggtt.c b/drivers/gpu/drm/xe/xe_ggtt.c
>>> index 7062115909f2..e7d474bd0cfe 100644
>>> --- a/drivers/gpu/drm/xe/xe_ggtt.c
>>> +++ b/drivers/gpu/drm/xe/xe_ggtt.c
>>> @@ -1,4 +1,4 @@
>>> -// SPDX-License-Identifier: MIT
>>> +/// SPDX-License-Identifier: MIT
>> what's this?
> happens when I have lagged connection to my dev machine. Will remove.
I really don't care when/how it was added
but it clearly shows that you don't check the diffs in patches before
sending them out and requesting a review
so asking again, please be more careful and mind the reviewers time
next prev parent reply other threads:[~2025-04-11 16:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 21:13 [PATCH v8 0/4] drm/xe/vf: Post-migration recovery of GGTT nodes and CTB Tomasz Lis
2025-04-09 21:13 ` [PATCH v8 1/4] drm/xe/vf: Divide GGTT ballooning into allocation and insertion Tomasz Lis
2025-04-10 16:54 ` Michal Wajdeczko
2025-04-11 14:35 ` Lis, Tomasz
2025-04-11 16:32 ` Michal Wajdeczko [this message]
2025-04-09 21:13 ` [PATCH v8 2/4] drm/xe/vf: Shifting GGTT area post migration Tomasz Lis
2025-04-10 17:13 ` Michal Wajdeczko
2025-04-11 14:37 ` Lis, Tomasz
2025-04-09 21:13 ` [PATCH v8 3/4] drm/xe/guc: Introduce enum with offsets for context register H2Gs Tomasz Lis
2025-04-10 17:16 ` Michal Wajdeczko
2025-04-09 21:13 ` [PATCH v8 4/4] drm/xe/vf: Fixup CTB send buffer messages after migration Tomasz Lis
2025-04-10 17:58 ` Michal Wajdeczko
2025-04-11 14:39 ` Lis, Tomasz
2025-04-11 16:45 ` Michal Wajdeczko
2025-04-09 21:18 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery of GGTT nodes and CTB (rev7) Patchwork
2025-04-09 21:19 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-09 21:20 ` ✓ CI.KUnit: success " Patchwork
2025-04-09 21:26 ` ✗ CI.Build: failure " Patchwork
2025-04-10 12:53 ` ✓ CI.Patch_applied: success " Patchwork
2025-04-10 12:54 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-10 12:55 ` ✓ CI.KUnit: success " Patchwork
2025-04-10 13:09 ` ✗ CI.Build: failure " 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=6394d86d-9daf-4955-9262-8c6a83b996c6@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.winiarski@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=tomasz.lis@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