From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 6CFE22095606B for ; Thu, 15 Mar 2018 02:52:24 -0700 (PDT) From: David Howells In-Reply-To: <20180313102056.GJ4043@hirez.programming.kicks-ass.net> References: <20180313102056.GJ4043@hirez.programming.kicks-ass.net> <152066488891.40260.14605734226832760468.stgit@dwillia2-desk3.amr.corp.intel.com> <152066493247.40260.10849841915366086021.stgit@dwillia2-desk3.amr.corp.intel.com> <20180311112725.GC4043@hirez.programming.kicks-ass.net> Subject: Re: [RFC][PATCH] sched/wait_bit: Introduce wait_var_event()/wake_up_var() MIME-Version: 1.0 Content-ID: <3395.1521107922.1@warthog.procyon.org.uk> Date: Thu, 15 Mar 2018 09:58:42 +0000 Message-ID: <3396.1521107922@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Peter Zijlstra Cc: linux-xfs , Jan Kara , linux-nvdimm , david , Linux Kernel Mailing List , Ralf Baechle , dhowells@redhat.com, Ingo Molnar , linux-fsdevel , Christoph Hellwig List-ID: Peter Zijlstra wrote: > > > Argh, no no no.. That whole wait_for_atomic_t thing is a giant > > > trainwreck already and now you're making it worse still. Your patch description needs to say why this isn't a trainwreck when you consider wait_for_atomic_t() to be one since it does things in a very similar way. David _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm