From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752218AbdLKVmZ (ORCPT ); Mon, 11 Dec 2017 16:42:25 -0500 Received: from ms.lwn.net ([45.79.88.28]:55754 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751123AbdLKVmX (ORCPT ); Mon, 11 Dec 2017 16:42:23 -0500 Date: Mon, 11 Dec 2017 14:42:21 -0700 From: Jonathan Corbet To: Elena Reshetova Cc: linux-doc@vger.kernel.org, peterz@infradead.org, linux-kernel@vger.kernel.org, keescook@chromium.org, david@fromorbit.com Subject: Re: [PATCH] docs: refcount_t documentation Message-ID: <20171211144221.189bd3c3@lwn.net> In-Reply-To: <1512470795-22626-1-git-send-email-elena.reshetova@intel.com> References: <1512470795-22626-1-git-send-email-elena.reshetova@intel.com> 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 5 Dec 2017 12:46:35 +0200 Elena Reshetova wrote: > Some functions from refcount_t API provide different > memory ordering guarantees that their atomic counterparts. > This adds a document outlining these differences ( > Documentation/core-api/refcount-vs-atomic.rst) as well as > some other minor improvements. I've applied this, thanks, it looks good. One thing I noticed, though, is that this landed in the core-api manual, while the refcount_t documentation is in the driver-api manual. The cross-references work just fine and such, but this still doesn't seem quite right. Probably what should be done is to have all the refcount_t material in core-api; I may do that if I get a moment. Thanks, jon