From: Catalin Marinas <catalin.marinas@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-efi@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: Fix dangling references to Documentation/arm64
Date: Wed, 14 Jun 2023 08:14:09 +0100 [thread overview]
Message-ID: <ZIlowXPqMcghhm4o@arm.com> (raw)
In-Reply-To: <20230613094606.334687-4-corbet@lwn.net>
On Tue, Jun 13, 2023 at 03:46:04AM -0600, Jonathan Corbet wrote:
> The arm64 documentation has moved under Documentation/arch/; fix up
> references in the arm64 subtree to match.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: linux-efi@vger.kernel.org
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2023-06-14 7:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 9:46 [PATCH 0/5] arm64: docs: Move the arm64 docs under Documentation/arch/ Jonathan Corbet
2023-06-13 9:46 ` [PATCH 1/5] docs: arm64: Move arm64 documentation " Jonathan Corbet
2023-06-14 1:29 ` Yanteng Si
2023-06-14 7:12 ` Catalin Marinas
2023-06-13 9:46 ` [PATCH 2/5] dt-bindings: fix dangling Documentation/arm64 reference Jonathan Corbet
2023-06-13 10:19 ` Rob Herring
2023-06-13 13:41 ` Rob Herring
2023-06-14 7:14 ` Catalin Marinas
2023-06-13 9:46 ` [PATCH 3/5] arm64: Fix dangling references to Documentation/arm64 Jonathan Corbet
2023-06-14 7:14 ` Catalin Marinas [this message]
2023-06-13 9:46 ` [PATCH 4/5] mm: Fix a dangling Documentation/arm64 reference Jonathan Corbet
2023-06-13 13:41 ` Mike Rapoport
2023-06-14 7:13 ` Catalin Marinas
2023-06-13 9:46 ` [PATCH 5/5] perf arm-spe: " Jonathan Corbet
2023-06-13 15:23 ` Arnaldo Carvalho de Melo
2023-06-14 7:15 ` Catalin Marinas
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=ZIlowXPqMcghhm4o@arm.com \
--to=catalin.marinas@arm.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).