public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: linux-doc@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH v2 3/7] arm64: Update Documentation/arm references
Date: Mon, 29 May 2023 08:48:52 -0600	[thread overview]
Message-ID: <20230529144856.102755-4-corbet@lwn.net> (raw)
In-Reply-To: <20230529144856.102755-1-corbet@lwn.net>

The Arm documentation has moved to Documentation/arch/arm; update
references under arch/arm64 to match.

Cc: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
 arch/arm64/Kconfig          | 2 +-
 arch/arm64/kernel/kuser32.S | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index b1201d25a8a4..377f50dda2de 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -1619,7 +1619,7 @@ config KUSER_HELPERS
 	  the system. This permits binaries to be run on ARMv4 through
 	  to ARMv8 without modification.
 
-	  See Documentation/arm/kernel_user_helpers.rst for details.
+	  See Documentation/arch/arm/kernel_user_helpers.rst for details.
 
 	  However, the fixed address nature of these helpers can be used
 	  by ROP (return orientated programming) authors when creating
diff --git a/arch/arm64/kernel/kuser32.S b/arch/arm64/kernel/kuser32.S
index 692e9d2e31e5..af046ceac22d 100644
--- a/arch/arm64/kernel/kuser32.S
+++ b/arch/arm64/kernel/kuser32.S
@@ -10,7 +10,7 @@
  * aarch32_setup_additional_pages() and are provided for compatibility
  * reasons with 32 bit (aarch32) applications that need them.
  *
- * See Documentation/arm/kernel_user_helpers.rst for formal definitions.
+ * See Documentation/arch/arm/kernel_user_helpers.rst for formal definitions.
  */
 
 #include <asm/unistd.h>
-- 
2.40.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-05-29 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 14:48 [PATCH v2 0/7] docs: Move Documentation/arm under Documentation/arch Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 1/7] arm: docs: Move Arm documentation to Documentation/arch/ Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 2/7] arm: update in-source documentation references Jonathan Corbet
2023-05-29 14:48 ` Jonathan Corbet [this message]
2023-05-29 14:48 ` [PATCH v2 4/7] mips: update a reference to a moved Arm Document Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 5/7] crypto: update some Arm documentation references Jonathan Corbet
2023-05-31 21:22   ` Jernej Škrabec
2023-05-29 14:48 ` [PATCH v2 6/7] docs: update some straggling Documentation/arm references Jonathan Corbet
2023-05-29 14:57   ` Greg Kroah-Hartman
2023-05-30  7:20   ` Nicolas.Ferre
2023-05-31 21:23   ` Jernej Škrabec
2023-06-14  7:04   ` Uwe Kleine-König
2023-05-29 14:48 ` [PATCH v2 7/7] dt-bindings: Update " Jonathan Corbet
2023-06-07 20:55   ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230529144856.102755-4-corbet@lwn.net \
    --to=corbet@lwn.net \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox