From: Peter Zijlstra <peterz@infradead.org>
To: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Cc: tzimmermann@suse.de, airlied@linux.ie,
gregkh@linuxfoundation.org, Boqun Feng <boqun.feng@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
mripard@kernel.org, linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
intel-gfx@lists.freedesktop.org, zackr@vmware.com
Subject: Re: [Intel-gfx] [PATCH 1/3] drm: use the lookup lock in drm_is_current_master
Date: Thu, 29 Jul 2021 16:45:10 +0200 [thread overview]
Message-ID: <YQK+9p+RIcFuzD3O@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <fbf2ec46-5ef5-7108-450a-13a7c48c30ce@gmail.com>
On Thu, Jul 29, 2021 at 10:32:13PM +0800, Desmond Cheong Zhi Xi wrote:
> Sounds good, will do. Thanks for the patch, Peter.
>
> Just going to make a small edit:
> s/LOCK_STAT_NOT_HELD/LOCK_STATE_NOT_HELD/
Bah, I knew I should've compile tested it :-), Thanks!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Cc: tzimmermann@suse.de, airlied@linux.ie,
Boqun Feng <boqun.feng@gmail.com>,
maarten.lankhorst@linux.intel.com,
LKML <linux-kernel@vger.kernel.org>,
mripard@kernel.org, linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
linux-kernel-mentees@lists.linuxfoundation.org,
intel-gfx@lists.freedesktop.org, zackr@vmware.com
Subject: Re: [PATCH 1/3] drm: use the lookup lock in drm_is_current_master
Date: Thu, 29 Jul 2021 16:45:10 +0200 [thread overview]
Message-ID: <YQK+9p+RIcFuzD3O@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <fbf2ec46-5ef5-7108-450a-13a7c48c30ce@gmail.com>
On Thu, Jul 29, 2021 at 10:32:13PM +0800, Desmond Cheong Zhi Xi wrote:
> Sounds good, will do. Thanks for the patch, Peter.
>
> Just going to make a small edit:
> s/LOCK_STAT_NOT_HELD/LOCK_STATE_NOT_HELD/
Bah, I knew I should've compile tested it :-), Thanks!
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Cc: tzimmermann@suse.de, airlied@linux.ie,
gregkh@linuxfoundation.org, Boqun Feng <boqun.feng@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm: use the lookup lock in drm_is_current_master
Date: Thu, 29 Jul 2021 16:45:10 +0200 [thread overview]
Message-ID: <YQK+9p+RIcFuzD3O@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <fbf2ec46-5ef5-7108-450a-13a7c48c30ce@gmail.com>
On Thu, Jul 29, 2021 at 10:32:13PM +0800, Desmond Cheong Zhi Xi wrote:
> Sounds good, will do. Thanks for the patch, Peter.
>
> Just going to make a small edit:
> s/LOCK_STAT_NOT_HELD/LOCK_STATE_NOT_HELD/
Bah, I knew I should've compile tested it :-), Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
Boqun Feng <boqun.feng@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-graphics-maintainer@vmware.com, zackr@vmware.com,
airlied@linux.ie, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
skhan@linuxfoundation.org, gregkh@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 1/3] drm: use the lookup lock in drm_is_current_master
Date: Thu, 29 Jul 2021 16:45:10 +0200 [thread overview]
Message-ID: <YQK+9p+RIcFuzD3O@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <fbf2ec46-5ef5-7108-450a-13a7c48c30ce@gmail.com>
On Thu, Jul 29, 2021 at 10:32:13PM +0800, Desmond Cheong Zhi Xi wrote:
> Sounds good, will do. Thanks for the patch, Peter.
>
> Just going to make a small edit:
> s/LOCK_STAT_NOT_HELD/LOCK_STATE_NOT_HELD/
Bah, I knew I should've compile tested it :-), Thanks!
next prev parent reply other threads:[~2021-07-29 14:45 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:29 [PATCH 0/3] drm, drm/vmwgfx: fixes and updates related to drm_master Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [PATCH 1/3] drm: use the lookup lock in drm_is_current_master Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 10:38 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 10:38 ` Daniel Vetter
2021-07-22 15:04 ` Boqun Feng
2021-07-22 15:04 ` [Intel-gfx] " Boqun Feng
2021-07-22 15:04 ` Boqun Feng
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` Daniel Vetter
2021-07-22 19:02 ` [Intel-gfx] " Daniel Vetter
2021-07-23 7:16 ` Boqun Feng
2021-07-23 7:16 ` [Intel-gfx] " Boqun Feng
2021-07-23 7:16 ` Boqun Feng
2021-07-27 14:37 ` Peter Zijlstra
2021-07-27 14:37 ` [Intel-gfx] " Peter Zijlstra
2021-07-27 14:37 ` Peter Zijlstra
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` Daniel Vetter
2021-07-29 7:00 ` [Intel-gfx] " Daniel Vetter
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:32 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:32 ` Desmond Cheong Zhi Xi
2021-07-29 14:45 ` Peter Zijlstra [this message]
2021-07-29 14:45 ` Peter Zijlstra
2021-07-29 14:45 ` Peter Zijlstra
2021-07-29 14:45 ` Peter Zijlstra
2021-07-22 9:29 ` [PATCH 2/3] drm: clarify lifetime/locking for drm_master's lease fields Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 10:35 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 10:35 ` Daniel Vetter
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 13:02 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 13:02 ` Desmond Cheong Zhi Xi
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` Daniel Vetter
2021-07-22 14:17 ` [Intel-gfx] " Daniel Vetter
2021-07-22 9:29 ` [PATCH 3/3] drm/vmwgfx: fix potential UAF in vmwgfx_surface.c Desmond Cheong Zhi Xi
2021-07-22 9:29 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 9:29 ` Desmond Cheong Zhi Xi
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 10:39 ` [Intel-gfx] " Daniel Vetter
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 10:39 ` Daniel Vetter
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` Zack Rusin
2021-07-22 19:17 ` [Intel-gfx] " Zack Rusin
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-23 6:44 ` [Intel-gfx] " Desmond Cheong Zhi Xi
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-23 6:44 ` Desmond Cheong Zhi Xi
2021-07-22 14:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm, drm/vmwgfx: fixes and updates related to drm_master Patchwork
2021-07-22 14:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-07-27 17:42 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm, drm/vmwgfx: fixes and updates related to drm_master (rev2) 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=YQK+9p+RIcFuzD3O@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=airlied@linux.ie \
--cc=boqun.feng@gmail.com \
--cc=desmondcheongzx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.