From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Nick Hu <nickhu@andestech.com>, Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: dev-tools: kmemleak: Update list of architectures
Date: Tue, 10 Mar 2020 11:32:22 -0600 [thread overview]
Message-ID: <20200310113222.2baa64ef@lwn.net> (raw)
In-Reply-To: <20200303194215.23756-1-j.neuschaefer@gmx.net>
On Tue, 3 Mar 2020 20:42:15 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> * Don't list powerpc twice (once as ppc)
> * Drop tile, which has been removed from the source tree
> * Mention arm64, nds32, arc, and xtensa
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> Documentation/dev-tools/kmemleak.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kmemleak.rst b/Documentation/dev-tools/kmemleak.rst
> index 3a289e8a1d12..fce262883984 100644
> --- a/Documentation/dev-tools/kmemleak.rst
> +++ b/Documentation/dev-tools/kmemleak.rst
> @@ -8,7 +8,8 @@ with the difference that the orphan objects are not freed but only
> reported via /sys/kernel/debug/kmemleak. A similar method is used by the
> Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
> user-space applications.
> -Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, ppc, mips, s390 and tile.
> +Kmemleak is supported on x86, arm, arm64, powerpc, sparc, sh, microblaze, mips,
> +s390, nds32, arc and xtensa.
>
> Usage
> -----
> --
> 2.20.1
>
Applied, thanks.
jon
prev parent reply other threads:[~2020-03-10 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 19:42 [PATCH] docs: dev-tools: kmemleak: Update list of architectures Jonathan Neuschäfer
2020-03-10 17:32 ` Jonathan Corbet [this message]
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=20200310113222.2baa64ef@lwn.net \
--to=corbet@lwn.net \
--cc=catalin.marinas@arm.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickhu@andestech.com \
/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).