Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp96016imm; Mon, 4 Jun 2018 13:43:29 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLJ2vrKAYRNGsJykHG+EG6KZL81+viHsffIvHY16bOpAvyaifcPQBKSBryrvxQzgOoo4icp X-Received: by 2002:a17:902:7484:: with SMTP id h4-v6mr22736720pll.154.1528145009702; Mon, 04 Jun 2018 13:43:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528145009; cv=none; d=google.com; s=arc-20160816; b=ItuWSll56nEpNfONEVlEtXtkXwONrGbDh5eET4WyrlQs03k/C9brU1wKTPT7jAnpUs ysNhlwQF7T3bv8XEulQYcF+k+5dkDzTM9rcfxR+eyRrgVJavDCAWOSKF56CgkUH+rqqN VCL83AIg+IR/gDvxx5FK1aFs+77zk25dczaZ+JvQqhrBOJxcSfPeYxsY5QiZXXFFmHvN bxWXYESp4+CEWun+pduKRGSV2KnQpinOJccdVh4JQNlhFTcXZstvAhZF+ObKAhZ3DBlS QVpOisD+7jruedeS2m0BWfdV4/1uXJJQKddxwoTkkw6TlSPX/bR0MV51vtUN7/PEM3/R gh/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:dkim-signature:arc-authentication-results; bh=8It/MtJOeY2CW6CMMgbDsiQ7Js4gnVkxFKWTzfgAhvg=; b=D0f+zrdqnOfMRtGQIJtcAdgnI6eEZfotFE4FflBYrTM+UK2SJFNv0IOFjbHXvcUpkJ N9veITPnlXMe8ZNUWbuo9k/kUvlbVCcBzcZgKY9k0dzkmbo5x8iEt1ymiV03kfRkYMe7 IdIij7IfLz6n0uD/qCBihwUt6p5/8jcEp8aCYofeLXlyB95VZ0eM4ciF/kKMZ1q+MXs6 o7T6Hr5uEals1SbHSf/EWEHL4CUuCGiO3OZcMMPPbKcZbKJMv0ZaQhbwayowUSua63ni +n7fg2NFTEyGEiqtN5zZ1NsmMF58m57JEFX79HnkU4cIwHDLZbWkbdHtjEF2OdAkxjF+ gbfg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@pmeerw.net header.s=mail header.b=e9DgmGxJ; dkim=fail header.i=@pmeerw.net header.s=mail header.b=aLf7UapX; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=pmeerw.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x12-v6si3847201pln.163.2018.06.04.13.43.06; Mon, 04 Jun 2018 13:43:29 -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; dkim=fail header.i=@pmeerw.net header.s=mail header.b=e9DgmGxJ; dkim=fail header.i=@pmeerw.net header.s=mail header.b=aLf7UapX; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=pmeerw.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751716AbeFDUlN (ORCPT + 99 others); Mon, 4 Jun 2018 16:41:13 -0400 Received: from ns.pmeerw.net ([84.19.176.117]:42844 "EHLO ns.pmeerw.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751375AbeFDUkw (ORCPT ); Mon, 4 Jun 2018 16:40:52 -0400 X-Greylist: delayed 486 seconds by postgrey-1.27 at vger.kernel.org; Mon, 04 Jun 2018 16:40:52 EDT Received: by ns.pmeerw.net (Postfix, from userid 113) id F0D7BE0427; Mon, 4 Jun 2018 22:32:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pmeerw.net; s=mail; t=1528144365; bh=kNCkHlne089wqOgEIMLPnMB7D/nsWE7eaIAApmhjgas=; h=From:To:Cc:Subject:Date:From; b=e9DgmGxJj1RxtDSbpTQ8p03j5oPM6WZLPqXGWpf6u8mANYpesTKZQy4RxbnQnb22Y vF8soxeyeuW3jJ2Yq++kbW5UJyGIRudyNeXIiCBPa2Pw98dczjWVbLTt3LbSIBdDaS GHOTP8xk9d1tLefNIHn1/fijbA/XDUFU1TuZWZns= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vps.pmeerw.net X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.1 Received: from vps.pmeerw.net (ns.pmeerw.net [IPv6:2001:1b60:2:23:1033:103:0:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmeerw@pmeerw.net) by ns.pmeerw.net (Postfix) with ESMTPSA id D18CCE00E4; Mon, 4 Jun 2018 22:32:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pmeerw.net; s=mail; t=1528144364; bh=kNCkHlne089wqOgEIMLPnMB7D/nsWE7eaIAApmhjgas=; h=From:To:Cc:Subject:Date:From; b=aLf7UapXfkKSc5lH6F3btZZ0Q6Ir0fXJHPeUSd6sFNlLbdzNFj2n9zWtyv9/qWhpS bpnB7tCAKB+xXBgY8P33D81bmYTn83zxsRl2/+YAFwf2UgKTbRIxXZzBO9eHmA5iza fUfG7TPcneU5/CQnZnsamhnu29US+M3swJCmAlZQ= From: Peter Meerwald-Stadler To: Johannes Berg Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, Peter Meerwald-Stadler Subject: [PATCH] rfkill: Correctly document rkill subfolder range as >= 0 in sysfs-class-rfkill Date: Mon, 4 Jun 2018 22:32:43 +0200 Message-Id: <20180604203243.28612-1-pmeerw@pmeerw.net> X-Mailer: git-send-email 2.11.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The first subfolder is rfkill0, hence rfkillX (X >= 0). Also fix two trivial typos. Signed-off-by: Peter Meerwald-Stadler --- Documentation/ABI/stable/sysfs-class-rfkill | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/ABI/stable/sysfs-class-rfkill b/Documentation/ABI/stable/sysfs-class-rfkill index e1ba4a104753..80151a409d67 100644 --- a/Documentation/ABI/stable/sysfs-class-rfkill +++ b/Documentation/ABI/stable/sysfs-class-rfkill @@ -11,7 +11,7 @@ KernelVersion: v2.6.22 Contact: linux-wireless@vger.kernel.org, Description: The rfkill class subsystem folder. Each registered rfkill driver is represented by an rfkillX - subfolder (X being an integer > 0). + subfolder (X being an integer >= 0). What: /sys/class/rfkill/rfkill[0-9]+/name @@ -48,8 +48,8 @@ Contact: linux-wireless@vger.kernel.org Description: Current state of the transmitter. This file was scheduled to be removed in 2014, but due to its large number of users it will be sticking around for a bit - longer. Despite it being marked as stabe, the newer "hard" and - "soft" interfaces should be preffered, since it is not possible + longer. Despite it being marked as stable, the newer "hard" and + "soft" interfaces should be preferred, since it is not possible to express the 'soft and hard block' state of the rfkill driver through this interface. There will likely be another attempt to remove it in the future. -- 2.11.0