Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp184920pxj; Tue, 15 Jun 2021 23:30:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzvK1dtqOlrvHmcyVg9bqI0T4b/75LnFEa1dwx/YEX7oc7bahOQ/7VIeg+RGIoC8YQ2kdcN X-Received: by 2002:a05:6e02:eee:: with SMTP id j14mr2587256ilk.238.1623825008695; Tue, 15 Jun 2021 23:30:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623825008; cv=none; d=google.com; s=arc-20160816; b=RDOk8QKjKGiznIILIdjkQYBX2ZMZ7h+s+hSxkeBrWfE34MJWVm8voGzTU2iHTG3oT/ o/N2uMyQokVW6EkS8hfqE5F11qum713ZewHFpzLRvyeKGXUuWhBGqfFMIk3IR+HaHW3I DrqysyyrBjlz9dU/n3N750wcWp94rnnyn2BsA+qNLnBHQStwEEO0TdUPa71Iw+fmKLug cfIFDGQcxMn/CexYkBDtNAgUvgQIW1+nvWs9PXHcrGB5tuoxCTosyOby+mf1aAQoAjPd NKQuPcrP0T5967jZ8z50VBOJNsJqQY6A9OBzfc3YHNBJirIaqui9LjLV3kbBw1wxMvK6 dq9Q== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=UeSq0qXoWE2CbbKJPqQ72thKOQPYujKD3Ph8PhK+Ux0=; b=knClvpGArnAU+LDtfm0CBlV3MWJYnHAwuQqq7JAcQJU2Uh17SDe567MxcGAjGBBCsl PI+i32Qx1Hdu6SNIP/xa6SJar/EMJU/xxOJqn/ST8Z2J7SOJBd3QlUPyGdO8d4VsnmZP AGibZEgFjo5/b+BU67whUksdO9w0r614CXbE2i2NImI/o10rZTCLGb3qv2h8Cwl3HO0S xs6Ow7cucQQfiwi8SePECEfcNNJyshudBknPFgrj56GOUdE3c1nPGlHZpKXZwabRzwmX nTcspAlyq/aafkZCfQ51rSsUhS0+r89+GBu8kAN9SAt2QY9F6fBNjY45oLxpoY3C8Xws sCPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=QSWSMAq5; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p24si1071985jal.79.2021.06.15.23.29.56; Tue, 15 Jun 2021 23:30:08 -0700 (PDT) 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=@kernel.org header.s=k20201202 header.b=QSWSMAq5; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231944AbhFPGbY (ORCPT + 99 others); Wed, 16 Jun 2021 02:31:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:59920 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231628AbhFPG3y (ORCPT ); Wed, 16 Jun 2021 02:29:54 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 80B1E613C7; Wed, 16 Jun 2021 06:27:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623824868; bh=asTkRaIynv0EXyPf2YOE4npgGc5H+lLigxxTS3UFkZ8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QSWSMAq5d4BVN94bdr8wyo8zjVTawMJ/78U+8jNzlfOCGOtF8zPIhd9npYIFCBLsD PhzSHqu/Jt7Xe55I5SmPUjgYHTn+XVNS6mQxUvsYHVv/KsfsvUryL7xrW/4a44Yodq rOx3e/r/VUCcgyDc3WpK74KdAyzLAfULeyKq1bRdfUSsmuDnGHKIymbSqGxsMQrKDx HHhgMJ2Nhg1lJGZw1aFVM42A17rwVDuD0VqwjxO73zdk6SZHxXaVLZgBhRW26+LUC9 qZ20smW1FD6do5ZQ5bwJz8GVH/KR8wLrKYG5xTQzg9qaL6hPWrfdVTA7gl8ETj7PoU bbZDT7XLoB91g== Received: by mail.kernel.org with local (Exim 4.94.2) (envelope-from ) id 1ltP1d-004kIM-Sz; Wed, 16 Jun 2021 08:27:45 +0200 From: Mauro Carvalho Chehab To: Jonathan Corbet , Linux Doc Mailing List Cc: Mauro Carvalho Chehab , linux-kernel@vger.kernel.org Subject: [PATCH v2 01/29] docs: devices.rst: better reference documentation docs Date: Wed, 16 Jun 2021 08:27:16 +0200 Message-Id: <5d9c9949a104d10b537a2d780bccad69a2dc58f9.1623824363.git.mchehab+huawei@kernel.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: Mauro Carvalho Chehab Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There's no need to use either :file: or :doc: tags for documentation, as automarkup.py automatically converts Documentation/*.rst into a cross-reference. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/pm/devices.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/driver-api/pm/devices.rst b/Documentation/driver-api/pm/devices.rst index 6b3bfd29fd84..d448cb57df86 100644 --- a/Documentation/driver-api/pm/devices.rst +++ b/Documentation/driver-api/pm/devices.rst @@ -217,7 +217,7 @@ system-wide transition to a sleep state even though its :c:member:`runtime_auto` flag is clear. For more information about the runtime power management framework, refer to -:file:`Documentation/power/runtime_pm.rst`. +Documentation/power/runtime_pm.rst. Calling Drivers to Enter and Leave System Sleep States @@ -655,7 +655,7 @@ been thawed. Generally speaking, the PM notifiers are suitable for performing actions that either require user space to be available, or at least won't interfere with user space. -For details refer to :doc:`notifiers`. +For details refer to Documentation/driver-api/pm/notifiers.rst. Device Low-Power (suspend) States @@ -726,7 +726,7 @@ it into account in any way. Devices may be defined as IRQ-safe which indicates to the PM core that their runtime PM callbacks may be invoked with disabled interrupts (see -:file:`Documentation/power/runtime_pm.rst` for more information). If an +Documentation/power/runtime_pm.rst for more information). If an IRQ-safe device belongs to a PM domain, the runtime PM of the domain will be disallowed, unless the domain itself is defined as IRQ-safe. However, it makes sense to define a PM domain as IRQ-safe only if all the devices in it @@ -805,7 +805,7 @@ The ``DPM_FLAG_MAY_SKIP_RESUME`` Driver Flag -------------------------------------------- During system-wide resume from a sleep state it's easiest to put devices into -the full-power state, as explained in :file:`Documentation/power/runtime_pm.rst`. +the full-power state, as explained in Documentation/power/runtime_pm.rst. [Refer to that document for more information regarding this particular issue as well as for information on the device runtime power management framework in general.] However, it often is desirable to leave devices in suspend after -- 2.31.1