From: Peter Zijlstra <peterz@infradead.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
intel-gfx@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 15/15] seqlock: drop seqcount_ww_mutex_t
Date: Thu, 7 Apr 2022 11:26:15 +0200 [thread overview]
Message-ID: <20220407092615.GJ2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220407085946.744568-16-christian.koenig@amd.com>
On Thu, Apr 07, 2022 at 10:59:46AM +0200, Christian König wrote:
> Daniel pointed out that this series removes the last user of
> seqcount_ww_mutex_t, so let's drop this.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, "Ingo Molnar" <mingo@redhat.com>,
"Waiman Long" <longman@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Christian König" <christian.koenig@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 15/15] seqlock: drop seqcount_ww_mutex_t
Date: Thu, 7 Apr 2022 11:26:15 +0200 [thread overview]
Message-ID: <20220407092615.GJ2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220407085946.744568-16-christian.koenig@amd.com>
On Thu, Apr 07, 2022 at 10:59:46AM +0200, Christian König wrote:
> Daniel pointed out that this series removes the last user of
> seqcount_ww_mutex_t, so let's drop this.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, "Ingo Molnar" <mingo@redhat.com>,
"Waiman Long" <longman@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Christian König" <christian.koenig@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 15/15] seqlock: drop seqcount_ww_mutex_t
Date: Thu, 7 Apr 2022 11:26:15 +0200 [thread overview]
Message-ID: <20220407092615.GJ2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220407085946.744568-16-christian.koenig@amd.com>
On Thu, Apr 07, 2022 at 10:59:46AM +0200, Christian König wrote:
> Daniel pointed out that this series removes the last user of
> seqcount_ww_mutex_t, so let's drop this.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2022-04-07 9:26 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 8:59 DMA-resv usage Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 01/15] dma-buf: add enum dma_resv_usage v4 Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 02/15] dma-buf: specify usage while adding fences to dma_resv obj v7 Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 9:14 ` Daniel Vetter
2022-04-07 9:14 ` [Intel-gfx] " Daniel Vetter
2022-04-07 9:14 ` Daniel Vetter
2022-04-07 13:08 ` Javier Martinez Canillas
2022-04-07 13:08 ` [Intel-gfx] " Javier Martinez Canillas
2022-04-07 13:13 ` Christian König
2022-04-07 13:13 ` [Intel-gfx] " Christian König
2022-04-07 13:16 ` Javier Martinez Canillas
2022-04-07 13:16 ` [Intel-gfx] " Javier Martinez Canillas
2022-04-07 8:59 ` [PATCH 03/15] dma-buf & drm/amdgpu: remove dma_resv workaround Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-20 3:56 ` Zack Rusin
2022-04-20 3:56 ` [Intel-gfx] " Zack Rusin
2022-04-20 3:56 ` Zack Rusin
2022-04-20 7:37 ` Christian König
2022-04-20 7:37 ` [Intel-gfx] " Christian König
2022-04-20 17:38 ` Zack Rusin
2022-04-20 17:38 ` [Intel-gfx] " Zack Rusin
2022-04-20 17:40 ` Christian König
2022-04-20 17:40 ` [Intel-gfx] " Christian König
2022-04-20 18:41 ` Zack Rusin
2022-04-20 18:41 ` [Intel-gfx] " Zack Rusin
2022-04-20 18:49 ` Christian König
2022-04-20 18:49 ` [Intel-gfx] " Christian König
2022-04-20 18:56 ` Christian König
2022-04-20 18:56 ` [Intel-gfx] " Christian König
2022-04-20 19:28 ` Zack Rusin
2022-04-20 19:28 ` [Intel-gfx] " Zack Rusin
2022-04-21 10:17 ` Christian König
2022-04-21 10:17 ` [Intel-gfx] " Christian König
2022-04-21 21:13 ` Zack Rusin
2022-04-21 21:13 ` [Intel-gfx] " Zack Rusin
2022-04-22 7:47 ` Christian König
2022-04-22 7:47 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 04/15] dma-buf: add DMA_RESV_USAGE_KERNEL v3 Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 05/15] drm/amdgpu: use DMA_RESV_USAGE_KERNEL Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 06/15] drm/radeon: " Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 07/15] drm/nouveau: only wait for kernel fences in nouveau_bo_vm_cleanup Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 08/15] RDMA: use DMA_RESV_USAGE_KERNEL Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 09/15] dma-buf: add DMA_RESV_USAGE_BOOKKEEP v3 Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 10/15] drm/amdgpu: use DMA_RESV_USAGE_BOOKKEEP Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 11/15] dma-buf: wait for map to complete for static attachments Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 12/15] drm/i915: drop bo->moving dependency Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-08 9:05 ` Jani Nikula
2022-04-08 9:05 ` [Intel-gfx] " Jani Nikula
2022-04-08 9:05 ` Jani Nikula
2022-04-08 9:27 ` Christian König
2022-04-08 9:27 ` [Intel-gfx] " Christian König
2022-04-08 9:27 ` Christian König
2022-04-08 9:33 ` Daniel Vetter
2022-04-08 9:33 ` Daniel Vetter
2022-04-08 9:33 ` [Intel-gfx] " Daniel Vetter
2022-04-08 9:39 ` Christian König
2022-04-08 9:39 ` [Intel-gfx] " Christian König
2022-04-08 9:39 ` Christian König
2022-04-08 10:15 ` Jani Nikula
2022-04-08 10:15 ` Jani Nikula
2022-04-08 10:15 ` [Intel-gfx] " Jani Nikula
2022-04-08 10:41 ` Christian König
2022-04-08 10:41 ` [Intel-gfx] " Christian König
2022-04-08 10:41 ` Christian König
2022-04-07 8:59 ` [PATCH 13/15] drm/ttm: remove bo->moving Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 14/15] dma-buf: drop seq count based update Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` [PATCH 15/15] seqlock: drop seqcount_ww_mutex_t Christian König
2022-04-07 8:59 ` [Intel-gfx] " Christian König
2022-04-07 8:59 ` Christian König
2022-04-07 9:19 ` Daniel Vetter
2022-04-07 9:19 ` [Intel-gfx] " Daniel Vetter
2022-04-07 9:19 ` Daniel Vetter
2022-04-07 11:48 ` Christian König
2022-04-07 11:48 ` [Intel-gfx] " Christian König
2022-04-07 9:26 ` Peter Zijlstra [this message]
2022-04-07 9:26 ` Peter Zijlstra
2022-04-07 9:26 ` Peter Zijlstra
2022-04-07 9:15 ` DMA-resv usage Daniel Vetter
2022-04-07 9:15 ` [Intel-gfx] " Daniel Vetter
2022-04-07 9:15 ` Daniel Vetter
2022-04-25 13:05 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [01/15] dma-buf: add enum dma_resv_usage v4 (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=20220407092615.GJ2731@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=will@kernel.org \
/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.