From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chen Ni <nichen@iscas.ac.cn>
Cc: <matthew.brost@intel.com>, <thomas.hellstrom@linux.intel.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/xe_vm: Convert comma to semicolon
Date: Fri, 27 Mar 2026 09:32:58 -0400 [thread overview]
Message-ID: <acaHCvc1G0g6jHY4@intel.com> (raw)
In-Reply-To: <20260327032923.649869-1-nichen@iscas.ac.cn>
On Fri, Mar 27, 2026 at 11:29:23AM +0800, Chen Ni wrote:
> Using a ',' in place of a ';' can have unintended side effects.
> Although that is not the case here, it seems best to use ';'
> unless ',' is intended.
>
> Found by inspection.
> No functional change intended.
> Compile tested only.
>
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
> ---
> drivers/gpu/drm/xe/xe_vm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index d96e0a0c5605..21844217dccd 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -626,9 +626,9 @@ void xe_vm_add_fault_entry_pf(struct xe_vm *vm, struct xe_pagefault *pf)
> e->address_precision = SZ_4K;
> e->access_type = pf->consumer.access_type;
> e->fault_type = FIELD_GET(XE_PAGEFAULT_TYPE_MASK,
> - pf->consumer.fault_type_level),
> + pf->consumer.fault_type_level);
> e->fault_level = FIELD_GET(XE_PAGEFAULT_LEVEL_MASK,
> - pf->consumer.fault_type_level),
> + pf->consumer.fault_type_level);
This code is not present in our tree.
In the xe_pagefault.c where this FIELD_GET commands are actually implemented,
the comma is the right way.
>
> list_add_tail(&e->list, &vm->faults.list);
> vm->faults.len++;
> --
> 2.25.1
>
next prev parent reply other threads:[~2026-03-27 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 3:29 [PATCH] drm/xe/xe_vm: Convert comma to semicolon Chen Ni
2026-03-27 13:32 ` Rodrigo Vivi [this message]
2026-03-30 13:52 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2026-03-30 21:16 ` [PATCH] " Lin, Shuicheng
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=acaHCvc1G0g6jHY4@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=nichen@iscas.ac.cn \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.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