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 4/4] drm/xe/vf: Fixup CTB send buffer messages after migration
Date: Fri, 11 Apr 2025 18:45:16 +0200 [thread overview]
Message-ID: <53283400-87a2-4c80-aad7-80b8166c30e2@intel.com> (raw)
In-Reply-To: <ffe2656f-a952-4fae-ad91-9ca9a4cb5678@intel.com>
On 11.04.2025 16:39, Lis, Tomasz wrote:
>
> On 10.04.2025 19:58, Michal Wajdeczko wrote:
>> On 09.04.2025 23:13, Tomasz Lis wrote:
...
>>> + */
>>> +static void ct_fixup_ggtt_in_message(struct xe_guc_ct *ct,
>>> + struct iosys_map *cmds, u32 head,
>>> + u32 len, u32 size, s64 shift)
>> -:84: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open
>> parenthesis
>> #84: FILE: drivers/gpu/drm/xe/xe_guc_ct.c:1655:
>> +static void ct_fixup_ggtt_in_message(struct xe_guc_ct *ct,
>> + struct iosys_map *cmds, u32 head,
>>
>> did you really run checkpatch.pl as promised ?
> Many functions got renamed on your request.
so it's my fault?
...
>>> +static int ct_fixup_ggtt_in_buffer(struct xe_guc_ct *ct, struct
>>> guc_ctb *h2g,
>>> + s64 shift, u32 *mhead, s32 avail)
>> -:135: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open
>> parenthesis
>> #135: FILE: drivers/gpu/drm/xe/xe_guc_ct.c:1706:
>> +static int ct_fixup_ggtt_in_buffer(struct xe_guc_ct *ct, struct guc_ctb
>> *h2g,
>> + s64 shift, u32 *mhead, s32 avail)
>
> will fix. And do checkpatch again.
>
not just 'again' or this 'next' time
it has to be run *each* time you plan to submit patches [1] so you want
waste CI and/or reviewers time
[1]
https://docs.kernel.org/process/submitting-patches.html#style-check-your-changes
next prev parent reply other threads:[~2025-04-11 16:45 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
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 [this message]
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=53283400-87a2-4c80-aad7-80b8166c30e2@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