Re: [PATCH] sched: Avoid spurious lock dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Qian Cai <cai@xxxxxx>
Subject: Re: [PATCH] sched: Avoid spurious lock dependencies
From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Date: Tue, 29 Oct 2019 13:44:53 +0100
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, bigeasy@xxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, thgarnie@xxxxxxxxxx, tytso@xxxxxxx, cl@xxxxxxxxx, penberg@xxxxxxxxxx, rientjes@xxxxxxxxxx, mingo@xxxxxxxxxx, will@xxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, keescook@xxxxxxxxxxxx
In-reply-to: <EE57FDCF-E3CD-4A0D-B0CC-C3CBAA7EBCBD@lca.pw>
References: <20191001091837.GK4536@hirez.programming.kicks-ass.net> <EE57FDCF-E3CD-4A0D-B0CC-C3CBAA7EBCBD@lca.pw>
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Oct 29, 2019 at 07:10:34AM -0400, Qian Cai wrote:
> 
> It looks like this patch has been forgotten forever. Do you need to
> repost, so Ingo might have a better chance to pick it up?

I've queued it now, sorry!

Follow-Ups:
- Re: [PATCH] sched: Avoid spurious lock dependencies
  - From: Qian Cai

References:
- [PATCH] sched: Avoid spurious lock dependencies
  - From: Peter Zijlstra
- Re: [PATCH] sched: Avoid spurious lock dependencies
  - From: Qian Cai

Prev by Date: AMD TLB errata, (Was: [PATCH RFC] mm: add MAP_EXCLUSIVE to create exclusive user mappings)
Next by Date: Re: [PATCH RFC v1 05/26] printk_safe: externalize printk_context
Previous by thread: Re: [PATCH] sched: Avoid spurious lock dependencies
Next by thread: Re: [PATCH] sched: Avoid spurious lock dependencies
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux