Received: by 10.192.165.148 with SMTP id m20csp4484170imm; Tue, 8 May 2018 09:08:57 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqstU0sRQ97k9p5WdZA1wsKoAmCiFROi5dVbuwJ4drEUcN6R/JBTi33idLdHGiCWk5EhDkz X-Received: by 2002:a63:381e:: with SMTP id f30-v6mr20885745pga.142.1525795734605; Tue, 08 May 2018 09:08:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525795734; cv=none; d=google.com; s=arc-20160816; b=Guv5QbMJVLUPmHXzxZdkB7mqE+cQ7wnsdPjqh6ctI/Qgnm9TCAhWRB2L75rafTwTFe ctQgTu5zokZL8E0tBLYw4DdCHRIkBKrt5Rr7HiIN0tm1E5UcRJyB4xUSt7j5gBj9X4Ib ObvE4EhjL4KFrR6fWWTcJ8POLYMIHdUo0LPSFHhIIO+1K8PHriZETK/9drVrTFFNXP6o 5ldxJrsCV6Xk7R88LTMFCkf2MRLbPdPgOahItRfNJtw6M+gjShT9MO4Tz3yQh5zFBXXI NYLGo5ix5W7Dai6Aalowe971sRwPy03SCgrwM7SlDzr1HyHUafL5i00RDE9JURln9Geu PjJw== 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:arc-authentication-results; bh=nNnFW+x1hx5GwZKd4H40k55ZMJOoyqro0BblzxkOYBY=; b=YMHzFeZMEmbKIMrjKZVP2/OOsqtjHBBUExuyO+oVuN130Cfnw9EnEXeXOI/TwfoJHM K/sLxkHbG6d75yck2hPCignW5X3fba4ajT7y3j/h4eKb+VSh6Uu6MDk/YXFM+qwSd74u ccUSAv6/5BzWSkRksjns2+MITs0EF4qhwtWT7Z1w0xN6XQGo0BMqIVBmdRYqmldkt3o3 nKux2gP+e8rsC9gV7xXGg7ZeZWr95QrxqrlvZiSfhMqr64iQk0AOUK5T6a5LvHgFZ6iI yoAodXiOdgS7jQdjWHbiCuUDu2eoVftzMcCLu4MGmqZ3yghP/asTNNHWxHgn0sxmGVBU LYUA== 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 r4si25401958pff.24.2018.05.08.09.08.39; Tue, 08 May 2018 09:08:54 -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 S1755421AbeEHQEP (ORCPT + 99 others); Tue, 8 May 2018 12:04:15 -0400 Received: from ms.lwn.net ([45.79.88.28]:35832 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754920AbeEHQEO (ORCPT ); Tue, 8 May 2018 12:04:14 -0400 Received: from localhost.localdomain (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 24906318; Tue, 8 May 2018 16:04:11 +0000 (UTC) Date: Tue, 8 May 2018 10:04:08 -0600 From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Alan Stern , Andrea Parri , Will Deacon , Peter Zijlstra , Boqun Feng , Nicholas Piggin , David Howells , Jade Alglave , Luc Maranget , "Paul E. McKenney" , Akira Yokosawa , Matthew Wilcox , Jeff Layton , Randy Dunlap , Elena Reshetova , "Tobin C. Harding" , SeongJae Park , Ingo Molnar , Helmut Grohne Subject: Re: [PATCH 05/18] docs: core-api: add cachetlb documentation Message-ID: <20180508100408.070fa171@lwn.net> In-Reply-To: <07b59879d34502828467f0190f941e23e08fdc81.1525684985.git.mchehab+samsung@kernel.org> References: <07b59879d34502828467f0190f941e23e08fdc81.1525684985.git.mchehab+samsung@kernel.org> Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) 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, 7 May 2018 06:35:41 -0300 Mauro Carvalho Chehab wrote: > The cachetlb.txt is already in ReST format. So, move it to the > core-api guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab I think we could do a better job of this by integrating it with the kerneldoc comments. Meanwhile, though, this is a step in the right direction, so I've applied it, thanks. jon