From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6BD12C2D0D2 for ; Tue, 24 Dec 2019 17:55:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4650B2071E for ; Tue, 24 Dec 2019 17:55:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=generalsoftwareinc-com.20150623.gappssmtp.com header.i=@generalsoftwareinc-com.20150623.gappssmtp.com header.b="Y/RNqmVr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726316AbfLXRz5 (ORCPT ); Tue, 24 Dec 2019 12:55:57 -0500 Received: from mail-vs1-f48.google.com ([209.85.217.48]:44069 "EHLO mail-vs1-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726183AbfLXRz5 (ORCPT ); Tue, 24 Dec 2019 12:55:57 -0500 Received: by mail-vs1-f48.google.com with SMTP id p6so12888871vsj.11 for ; Tue, 24 Dec 2019 09:55:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=generalsoftwareinc-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=qAQiP9imOCYoI9n+AcXLTq7zfRlO4PU4XGOsmdEoMlw=; b=Y/RNqmVrVUQbA5WiGAT0yPj2GRXKyVySRqoZQ8ImgqyLqczo1wfmav26rKuUGyQ516 Q1bkXCLSJBl0/iiTeM2HvNaallxah2FB1etjsaVZn79Rk7GLp5vpBYsEt9lGhv5WnF4r hTIfYnmxPkDXitFkkdcxfnERTEnSRr0xClDC0EUVaDYePAX31Myl2Ez22W0W4uv8Rqx+ 8iwHxvpFYvqaed4YEvkY/Q/6qSB6crRihoTlPBvGz85b8reOmFSGpXleWuWr/xYZH74z iM5N62OvJeByoNmLxcbxe4OKDTEvqIGFOt7+p86pXyW6vKibv7OQ4BNn6R7EmR9j4EdZ f5uA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=qAQiP9imOCYoI9n+AcXLTq7zfRlO4PU4XGOsmdEoMlw=; b=rgx33rZ4tVaeQs7Ay3ned3u6hHr80sZ8ygMbek6vCdWvQBvy56Zac/jeSrvCBkOV8w zuDMU3W0IiQDrtureEE6wp0L3Wausm2dehwlkeQ6QUluGudHwnEbIjsXSpe6CKCTweOi LZrnIDO65sHVfKgI6psm2ty0oZYwbemxZmoo303eLsXcWZT+Js+ivEyLFFCQMXMdOezQ XW3RfbeEcQQUDH2dR4kFexnmc9hJdoGyfEKU0lYQciZ0TRmoDohhk/KGQIHdkwCPBUzi OX24flgxdLTisJSo/BmTUIdUlvjP+aLmo7sQ/8M2ssGbhBma/wms/xQih5zA4fVHoO2O hvLg== X-Gm-Message-State: APjAAAU3960uOLa49ugf+uEXw3d7blZgPDAOYFVFItDkQUo1vnOpIti8 fpzu5ylPb2GhGf00oKv75bA5eg== X-Google-Smtp-Source: APXvYqx6KjAfDoXnQzQCFG4LBLgdECoUQzcLgp3MLB3z6dzXOnZRCdq++5kRrv/au+YCw4o7TtJh7w== X-Received: by 2002:a05:6102:5ea:: with SMTP id w10mr6042478vsf.183.1577210156063; Tue, 24 Dec 2019 09:55:56 -0800 (PST) Received: from frank-laptop ([172.97.41.74]) by smtp.gmail.com with ESMTPSA id b4sm3003190vsr.5.2019.12.24.09.55.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Dec 2019 09:55:55 -0800 (PST) Date: Tue, 24 Dec 2019 12:55:54 -0500 From: "Frank A. Cancio Bello" To: Steven Rostedt , Ingo Molnar , Jonathan Corbet , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: joel@joelfernandes.org, saiprakash.ranjan@codeaurora.org, nachukannan@gmail.com Subject: [PATCH 0/3] docs: ftrace: Fix minor issues in the doc Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I didn't want to be pushy with these minor fixes but occur to me now that, even all seem to be clear in the latest version of the RFC (v2) related to these fixes, a clean patchset could be expected after the RFC. So here we go: Clarifies the RAM footprint of buffer_size_kb without getting into implementation details. Fix typos and a small notation mistakes in the doc. Changes in this patchset (since RFC v2) - Take out the notation mistake into its own commit because it is not a typo. Changes in RFC v2: - Removes implementation description of the RAM footprint of buffer_size_kb, but still make the corresponded clarification. - Removes a patch that was just for illustration purposes because Steven already got the issue that I was referring to. - Adds a patch to fix other typos in the doc. Frank A. Cancio Bello (3): docs: ftrace: Clarify the RAM impact of buffer_size_kb docs: ftrace: Fix typos docs: ftrace: Fix small notation mistake Documentation/trace/ftrace.rst | 9 +++++---- Documentation/trace/ring-buffer-design.txt | 2 +- 2 files changed, 6 insertions(+), 5 deletions(-) -- 2.17.1