Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1043647ybe; Mon, 2 Sep 2019 13:22:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqywfo8NnRv+FkbTXVcFxrVsqhzhbvk9ixLZHAuNzKsnlZxqZlCYjhTQRKr/U8Tg7WQB37NX X-Received: by 2002:a17:90a:b781:: with SMTP id m1mr14103094pjr.141.1567455755649; Mon, 02 Sep 2019 13:22:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567455755; cv=none; d=google.com; s=arc-20160816; b=doKGsQMRpgwZ0D251ZMXWOpZ+gk10zG7vknTrWwiFThD1ZyaPqL3gH+E4Zlrxf3WqO zY6coOOYHsPngDuSd7Ba9JdkJjLNseX/6GT+3jX9Y8mhb6bRZhSCv1KuVXGlrSM8vLGE 6hZ2JbSMV9kH0s8Y+Pc4kSMx9WcDVY79TA94tHgxLGwOUQJrcZs79kCtDnEqeGVoBLCk zaWZCUSlHvpbHG92yODGAlhHfNJJoyXbNM7ekVGaFr8PaEqpM7/WXF46Umh8Rl2ccn+z zuxNuHl4C0wxT3wm3nibxMBJdaXbez+tROAa1Cw2yLfNRS7EOX7kc4Ove/VKIyEdtBIQ eVCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=yRs4dxn/0eJD4FD1+LhNITd324xLnk1rsZfwY54jf9s=; b=C0C1ps7OW1HUfqNTxFQnfty8H3HNbSWjEAzhWcBS7q/tx/Pt/ChttBCzkPpp3IlkTY 4Bv2S0RGCOPLo3da/UL7pQLdKbD/z2VJSdykttZVlDhBwiEcIauexquM/OCC0xQG/q3C 9FwoEXzHysRDzLxA+JBZTcBsaTBMrO01DApSNUDd+uFP19bei5bOq8rbze5vILVzFDtV dkEX/p6QpdIi9k8pVrkatTk3EfXFdhHXSyPBZtayiATY7S0AV/SYMts4rHEesx3dbAVQ OxtZ21sUzNO5Yw5py3WQ2XBW8O7Y7VQM02mh9QTGlpkRLikHmECxryk/iOxwNSpqtx/j zCBg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u38si12617337pgn.79.2019.09.02.13.22.20; Mon, 02 Sep 2019 13:22:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727281AbfIBUVf (ORCPT + 99 others); Mon, 2 Sep 2019 16:21:35 -0400 Received: from ms.lwn.net ([45.79.88.28]:56534 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726518AbfIBUVf (ORCPT ); Mon, 2 Sep 2019 16:21:35 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 4487530D; Mon, 2 Sep 2019 20:21:34 +0000 (UTC) Date: Mon, 2 Sep 2019 14:21:33 -0600 From: Jonathan Corbet To: Federico Vaga Cc: Ingo Molnar , Peter Zijlstra , Ingo Molnar , Will Deacon , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] doc:lock: remove reference to clever use of read-write lock Message-ID: <20190902142133.37e106af@lwn.net> In-Reply-To: <4627860.yBeiQmOknq@harkonnen> References: <20190831134116.25417-1-federico.vaga@vaga.pv.it> <2216492.xyESGPMPG3@pcbe13614> <20190902181010.GA35858@gmail.com> <4627860.yBeiQmOknq@harkonnen> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 02 Sep 2019 21:19:24 +0200 Federico Vaga wrote: > > > I am not used to the mathematical English jargon. It make sense, but then > > > I > > > would replace it with "If and only if": for clarity. > > > > While it's used in a number of places and it's pretty common wording > > overall in the literature, I agree that we should probably change this in > > locking API user facing documentation. > > I would say not only in locking/. The argument is valid for the entire > Documentation/. I wait for Jon's opinion before proceeding. I don't really have a problem with "iff"; it doesn't seem like *that* obscure a term to me. But if you want spell it out, I guess I don't have a problem with that. We can change it - iff you send a patch to do it :) Thanks, jon