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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 610CEC2BB41 for ; Tue, 16 Aug 2022 08:21:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230501AbiHPIU7 (ORCPT ); Tue, 16 Aug 2022 04:20:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58260 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232537AbiHPIUC (ORCPT ); Tue, 16 Aug 2022 04:20:02 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CDA022CDD9; Mon, 15 Aug 2022 23:04:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1660629900; x=1692165900; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=xPNIrkcFCfvS9ZaGQOj/prDr79CDpw4QxyV4FdP7r80=; b=cqzVFe+kUaMUBpkFd/9GzucLOcRqfobvCA2QLh7jWuMApeE2FVaIgOlY w1JTjdtKyNnWoAecRzWygG5hPcLnupaMIlqXNfIFDcOZUn7VBbptPyb70 Gqjb3LwBC09Uhw+S2mbVicXX1AmshXk4cS90Kjg9wmWArn1w9Ob4EI8GK G+cqn1wx85XMArrKF+PmQZLQqt5/EqjOraqUZ7ofunE5vQzKH22WyXSGK BGdGbURZd7euua606GwJb3XUwc6zfUPFyrQINenZF9tSI64SLSEgIOVH8 9qumTUUUPyCodvuuTihg5mQTn9+H6jt1DQzSdBpZWx9zuV4IaQAU0phnS Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10440"; a="290887403" X-IronPort-AV: E=Sophos;i="5.93,240,1654585200"; d="scan'208";a="290887403" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Aug 2022 23:04:56 -0700 X-IronPort-AV: E=Sophos;i="5.93,240,1654585200"; d="scan'208";a="666967947" Received: from asmit6-mobl2.ger.corp.intel.com (HELO [10.0.2.15]) ([10.252.38.228]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Aug 2022 23:04:53 -0700 Message-ID: Date: Tue, 16 Aug 2022 09:04:48 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.11.0 Subject: Re: perf tools man pages on the web Content-Language: en-US To: Namhyung Kim , Ian Rogers Cc: Arnaldo Carvalho de Melo , Jiri Olsa , Jonathan Corbet , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , "linux-perf-users@vger.kernel.org" , LKML References: From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-perf-users@vger.kernel.org On 16/08/22 08:07, Namhyung Kim wrote: > Hi Ian and Adrian, > > On Mon, Aug 15, 2022 at 7:56 AM Ian Rogers wrote: >> >> On Mon, Aug 15, 2022 at 5:05 AM Adrian Hunter wrote: >>> >>> Hi >>> >>> I notice man pages on man7.org e.g. >>> >>> https://www.man7.org/linux/man-pages/man1/perf.1.html >>> >>> do not get updated every release, and I wondered if the perf tools >>> man pages should also be under: >>> >>> https://docs.kernel.org/tools/index.html >>> >>> Thoughts? >> >> Sounds good to me. I'm assuming it would be some kind of build step >> that would take the man pages and add them to what linux-doc needs? > > I guess it's the RST format. I'm not sure if there's a converter > from asciidoc to RST. Could use the html files that are already generated by: make -C perf/tools html > Anyway having the perf man pages in the > tools section looks good. > >> >> Fwiw, there has been some effort to try to improve the wiki: >> https://perf.wiki.kernel.org/index.php/Main_Page >> For example, the useful links are now broken apart and have more >> links, there is a work-in-progress glossary. Perhaps there can be some >> guidance on what to capture and where. > > Thanks for working on this. I really need to take a look... > > Thanks, > Namhyung