From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: airlied@gmail.com, akpm@linux-foundation.org,
alison.schofield@intel.com, andrew+netdev@lunn.ch,
andriy.shevchenko@linux.intel.com, arend.vanspriel@broadcom.com,
bp@alien8.de, brcm80211-dev-list.pdl@broadcom.com,
brcm80211@lists.linux.dev, colin.i.king@gmail.com,
cvam0000@gmail.com, dan.j.williams@intel.com,
dave.hansen@linux.intel.com, dave.jiang@intel.com,
dave@stgolabs.net, davem@davemloft.net,
dri-devel@lists.freedesktop.org, edumazet@google.com,
gregkh@linuxfoundation.org, guanwentao@uniontech.com,
hpa@zytor.com, ilpo.jarvinen@linux.intel.com,
intel-xe@lists.freedesktop.org, ira.weiny@intel.com,
j@jannau.net, jeff.johnson@oss.qualcomm.com, jgross@suse.com,
jirislaby@kernel.org, johannes.berg@intel.com,
jonathan.cameron@huawei.com, kuba@kernel.org, kvalo@kernel.org,
kvm@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-wireless@vger.kernel.org, linux@treblig.org,
lucas.demarchi@intel.com, marcin.s.wojtas@gmail.com,
ming.li@zohomail.com, mingo@kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, niecheng1@uniontech.com,
oleksandr_tyshchenko@epam.com, pabeni@redhat.com,
pbonzini@redhat.com, quic_ramess@quicinc.com,
ragazenta@gmail.com, rodrigo.vivi@intel.com, seanjc@google.com,
shenlichuan@vivo.com, simona@ffwll.ch, sstabellini@kernel.org,
tglx@linutronix.de, vishal.l.verma@intel.com,
wangyuli@deepin.org, x86@kernel.org,
xen-devel@lists.xenproject.org, yujiaoliang@vivo.com,
zhanjun@uniontech.com
Subject: Re: [PATCH v3 3/8] drm/xe: Fix typo "notifer"
Date: Tue, 22 Jul 2025 11:24:15 +0200 [thread overview]
Message-ID: <ffd58e1a8b51c98cac9be49e85d367f1a3a24c2d.camel@linux.intel.com> (raw)
In-Reply-To: <94190C5F54A19F3E+20250722073431.21983-3-wangyuli@uniontech.com>
On Tue, 2025-07-22 at 15:34 +0800, WangYuli wrote:
> There is a spelling mistake of 'notifer' in the comment which
> should be 'notifier'.
>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/xe/xe_vm_types.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm_types.h
> b/drivers/gpu/drm/xe/xe_vm_types.h
> index 1979e9bdbdf3..0ca27579fd1f 100644
> --- a/drivers/gpu/drm/xe/xe_vm_types.h
> +++ b/drivers/gpu/drm/xe/xe_vm_types.h
> @@ -259,7 +259,7 @@ struct xe_vm {
> * up for revalidation. Protected from access with
> the
> * @invalidated_lock. Removing items from the list
> * additionally requires @lock in write mode, and
> adding
> - * items to the list requires either the
> @userptr.notifer_lock in
> + * items to the list requires either the
> @userptr.notifier_lock in
> * write mode, OR @lock in write mode.
> */
> struct list_head invalidated;
next prev parent reply other threads:[~2025-07-22 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 7:27 [PATCH v3 0/8] treewide: Fix typo "notifer" WangYuli
2025-07-22 7:34 ` [PATCH v3 1/8] KVM: x86: " WangYuli
2025-07-22 7:34 ` [PATCH v3 2/8] cxl: mce: " WangYuli
2025-07-22 7:34 ` [PATCH v3 3/8] drm/xe: " WangYuli
2025-07-22 9:24 ` Thomas Hellström [this message]
2025-07-22 7:34 ` [PATCH v3 4/8] net: mvneta: " WangYuli
2025-07-22 7:34 ` [PATCH v3 5/8] wifi: brcmfmac: " WangYuli
2025-07-22 7:34 ` [PATCH v3 6/8] serial: 8250_dw: " WangYuli
2025-07-22 7:34 ` [PATCH v3 7/8] xen/xenbus: " WangYuli
2025-07-22 7:34 ` [PATCH v3 8/8] scripts/spelling.txt: Add notifer||notifier to spelling.txt WangYuli
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=ffd58e1a8b51c98cac9be49e85d367f1a3a24c2d.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arend.vanspriel@broadcom.com \
--cc=bp@alien8.de \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=colin.i.king@gmail.com \
--cc=cvam0000@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=guanwentao@uniontech.com \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=ira.weiny@intel.com \
--cc=j@jannau.net \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jgross@suse.com \
--cc=jirislaby@kernel.org \
--cc=johannes.berg@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lucas.demarchi@intel.com \
--cc=marcin.s.wojtas@gmail.com \
--cc=ming.li@zohomail.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=pabeni@redhat.com \
--cc=pbonzini@redhat.com \
--cc=quic_ramess@quicinc.com \
--cc=ragazenta@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=seanjc@google.com \
--cc=shenlichuan@vivo.com \
--cc=simona@ffwll.ch \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=vishal.l.verma@intel.com \
--cc=wangyuli@deepin.org \
--cc=wangyuli@uniontech.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yujiaoliang@vivo.com \
--cc=zhanjun@uniontech.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;
as well as URLs for NNTP newsgroup(s).