Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp978128pxb; Wed, 3 Mar 2021 23:16:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJzH9rX/Q93A9AhW8JEknOniZcQkKoEFw3SMdxvc4N28zYH1PYl5ftZbUI/yubBoc1cWsFdn X-Received: by 2002:aa7:c346:: with SMTP id j6mr2809173edr.386.1614842170487; Wed, 03 Mar 2021 23:16:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614842170; cv=none; d=google.com; s=arc-20160816; b=QZpeBRO5mzdvLukW250VloNgjT2A1AMYKox318yZI/s53pQyfgZAizj0MI6OkE2qLV VDvgEXTD9xRoNkmYT+DCStCssN2+Aak4U0hX8HM2eVNI3E9uRUQvqTwfIGLnPWibzRgJ 75q+TV7ifiMR2kfixRYW3g7Uh8gncN6yNvD3LDeJ2F5TwoyQfDdy5kDWH4mfc24mMvRN xB/WZ2wLuEkdxhtuEjnEALo+jhx2k0vdBHSTRNRRDBbzAlhACOi6wfrqOrMrT6re+NA7 jKbFbGHC35WIDog+vcsBd4VpB+MgRSUIqOTq/vFCn1cSMzM/9O8tHgAUVPdMZAMuc5a9 5wrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=8TMyUR3FxKZj4Yww6Be0VR13DVAO/4GEltOF7rXLte4=; b=zompjLg2kpHtG1jDRsr+wiFxThrNMvk1c/oj3ook1SlBmtrxFA9lj9V2EP6JMo6LfJ HtsL72MpedaKcSv3m4QBeD5wKJYaPGy5fu9igZ7bMYRArCp/4YRQjCBoi8glbK/WDgtS lyBCcN5yZbFnB1lV9651ealKtmUvJivANClmUNk6SlWDzdQrK4Cz47vr5rlOYEtChUWO BWbQlbwMFXJyYmGoYL+M3nXhq89cskHLjXgs3G5t+3Xbuxl/Im/h0ub4WTcjrad9XkGh eioM34CVnfTt2HFN91rL6mkDaRc9miq1vxC3dYtQvG58MGREtpXmw3RgALZpY2RLBxSo amQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@posteo.net header.s=2017 header.b="ZlmCR/4U"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=posteo.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id jg13si17592384ejc.126.2021.03.03.23.15.48; Wed, 03 Mar 2021 23:16:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@posteo.net header.s=2017 header.b="ZlmCR/4U"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=posteo.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2360122AbhCBWQy (ORCPT + 99 others); Tue, 2 Mar 2021 17:16:54 -0500 Received: from mout01.posteo.de ([185.67.36.65]:57565 "EHLO mout01.posteo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1446251AbhCBU2k (ORCPT ); Tue, 2 Mar 2021 15:28:40 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id AE2C9160064 for ; Tue, 2 Mar 2021 21:27:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1614716842; bh=8mi09Rx1C6p0vrdpYJiMwlPPYaMYUrw/IsAC+AOdZ3o=; h=From:To:Cc:Subject:Date:From; b=ZlmCR/4U1dJajTUv4+e58feNY13LkX+mwtu/zbSGTOzylPFIgloG5Q0bHItsStt24 iwYKYXjMySy6JRkOe9sy7tsKgtc+0qFx0bt6osoBQ/TGLoY05h1uUhFQxn4fTVvv+L CEYJcpmYDqxAZnYmjUc7+bvNQDdiVL/cznESLifVUgjakpvye5isVki1VVoSEuU6dX N6USuljVw9s706tvTeYsDue6imAlE/9KlmSmk6uGiYf6jLJXcq3HBpckXH96RqrQUF BAooiCIxgBI5DjHRLQwBjetAfofB+W6klLnxPKU7MDAGZu85xWkYn2BFGMkLteye31 G1zl2fXwpPhkw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4DqpZx5dX6z6tmT; Tue, 2 Mar 2021 21:27:21 +0100 (CET) From: Mark O'Donovan To: linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Mark O'Donovan Subject: [PATCH] Documentation: Add leading slash to some paths Date: Tue, 2 Mar 2021 20:25:40 +0000 Message-Id: <20210302202539.103853-1-shiftee@posteo.net> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Change multiple sys/xyz to /sys/xyz Signed-off-by: Mark O'Donovan --- Documentation/admin-guide/mm/numaperf.rst | 2 +- Documentation/fb/fbcon.rst | 4 ++-- Documentation/hid/intel-ish-hid.rst | 2 +- Documentation/leds/leds-lm3556.rst | 28 +++++++++++------------ 4 files changed, 18 insertions(+), 18 deletions(-) diff --git a/Documentation/admin-guide/mm/numaperf.rst b/Documentation/admin-guide/mm/numaperf.rst index c2f826409bf0..166697325947 100644 --- a/Documentation/admin-guide/mm/numaperf.rst +++ b/Documentation/admin-guide/mm/numaperf.rst @@ -151,7 +151,7 @@ Each cache level's directory provides its attributes. For example, the following shows a single cache level and the attributes available for software to query:: - # tree sys/devices/system/node/node0/memory_side_cache/ + # tree /sys/devices/system/node/node0/memory_side_cache/ /sys/devices/system/node/node0/memory_side_cache/ |-- index1 | |-- indexing diff --git a/Documentation/fb/fbcon.rst b/Documentation/fb/fbcon.rst index 57f66de2f7e1..212f7003cfba 100644 --- a/Documentation/fb/fbcon.rst +++ b/Documentation/fb/fbcon.rst @@ -207,9 +207,9 @@ Documentation/driver-api/console.rst. To summarize: Echo a value to the bind file that represents the framebuffer console driver. So assuming vtcon1 represents fbcon, then:: - echo 1 > sys/class/vtconsole/vtcon1/bind - attach framebuffer console to + echo 1 > /sys/class/vtconsole/vtcon1/bind - attach framebuffer console to console layer - echo 0 > sys/class/vtconsole/vtcon1/bind - detach framebuffer console from + echo 0 > /sys/class/vtconsole/vtcon1/bind - detach framebuffer console from console layer If fbcon is detached from the console layer, your boot console driver (which is diff --git a/Documentation/hid/intel-ish-hid.rst b/Documentation/hid/intel-ish-hid.rst index f6ce44ff611d..7a851252267a 100644 --- a/Documentation/hid/intel-ish-hid.rst +++ b/Documentation/hid/intel-ish-hid.rst @@ -345,7 +345,7 @@ Documentation/ABI/testing/sysfs-bus-iio for IIO ABIs to user space. To debug ISH, event tracing mechanism is used. To enable debug logs:: echo 1 > /sys/kernel/debug/tracing/events/intel_ish/enable - cat sys/kernel/debug/tracing/trace + cat /sys/kernel/debug/tracing/trace 3.8 ISH IIO sysfs Example on Lenovo thinkpad Yoga 260 ----------------------------------------------------- diff --git a/Documentation/leds/leds-lm3556.rst b/Documentation/leds/leds-lm3556.rst index 1ef17d7d800e..32e3983473ba 100644 --- a/Documentation/leds/leds-lm3556.rst +++ b/Documentation/leds/leds-lm3556.rst @@ -23,7 +23,7 @@ from 93.75 mA to 1500 mA.The Flash currents are adjusted via the CURRENT CONTROL REGISTER(0x09).Flash mode is activated by the ENABLE REGISTER(0x0A), or by pulling the STROBE pin HIGH. -LM3556 Flash can be controlled through sys/class/leds/flash/brightness file +LM3556 Flash can be controlled through /sys/class/leds/flash/brightness file * if STROBE pin is enabled, below example control brightness only, and ON / OFF will be controlled by STROBE pin. @@ -32,17 +32,17 @@ Flash Example: OFF:: - #echo 0 > sys/class/leds/flash/brightness + #echo 0 > /sys/class/leds/flash/brightness 93.75 mA:: - #echo 1 > sys/class/leds/flash/brightness + #echo 1 > /sys/class/leds/flash/brightness ... 1500 mA:: - #echo 16 > sys/class/leds/flash/brightness + #echo 16 > /sys/class/leds/flash/brightness Torch Mode ^^^^^^^^^^ @@ -51,7 +51,7 @@ In Torch Mode, the current source(LED) is programmed via the CURRENT CONTROL REGISTER(0x09).Torch Mode is activated by the ENABLE REGISTER(0x0A) or by the hardware TORCH input. -LM3556 torch can be controlled through sys/class/leds/torch/brightness file. +LM3556 torch can be controlled through /sys/class/leds/torch/brightness file. * if TORCH pin is enabled, below example control brightness only, and ON / OFF will be controlled by TORCH pin. @@ -59,22 +59,22 @@ Torch Example: OFF:: - #echo 0 > sys/class/leds/torch/brightness + #echo 0 > /sys/class/leds/torch/brightness 46.88 mA:: - #echo 1 > sys/class/leds/torch/brightness + #echo 1 > /sys/class/leds/torch/brightness ... 375 mA:: - #echo 8 > sys/class/leds/torch/brightness + #echo 8 > /sys/class/leds/torch/brightness Indicator Mode ^^^^^^^^^^^^^^ -Indicator pattern can be set through sys/class/leds/indicator/pattern file, +Indicator pattern can be set through /sys/class/leds/indicator/pattern file, and 4 patterns are pre-defined in indicator_pattern array. According to N-lank, Pulse time and N Period values, different pattern wiill @@ -87,13 +87,13 @@ Indicator pattern example: pattern 0:: - #echo 0 > sys/class/leds/indicator/pattern + #echo 0 > /sys/class/leds/indicator/pattern ... pattern 3:: - #echo 3 > sys/class/leds/indicator/pattern + #echo 3 > /sys/class/leds/indicator/pattern Indicator brightness can be controlled through sys/class/leds/indicator/brightness file. @@ -102,17 +102,17 @@ Example: OFF:: - #echo 0 > sys/class/leds/indicator/brightness + #echo 0 > /sys/class/leds/indicator/brightness 5.86 mA:: - #echo 1 > sys/class/leds/indicator/brightness + #echo 1 > /sys/class/leds/indicator/brightness ... 46.875mA:: - #echo 8 > sys/class/leds/indicator/brightness + #echo 8 > /sys/class/leds/indicator/brightness Notes ----- -- 2.25.1