From: Catalin Marinas <catalin.marinas@arm.com>
To: Rustam Kovhaev <rkovhaev@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: kmemleak: add more details about kmemleak usage
Date: Fri, 18 Jun 2021 15:34:01 +0100 [thread overview]
Message-ID: <20210618143401.GD16116@arm.com> (raw)
In-Reply-To: <20210617210420.392412-1-rkovhaev@gmail.com>
On Thu, Jun 17, 2021 at 02:04:20PM -0700, Rustam Kovhaev wrote:
> a user may need to initiate a manual scan twice via debugfs before
> kmemleak reports an orphan object.
> this is mentioned in Testing section, let's mention this again in the
> Usage section for better visibility.
>
> Link: https://lore.kernel.org/lkml/YMpEtyUP0vuWo9HV@nuc10/
> Signed-off-by: Rustam Kovhaev <rkovhaev@gmail.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
prev parent reply other threads:[~2021-06-18 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 21:04 [PATCH] docs: kmemleak: add more details about kmemleak usage Rustam Kovhaev
2021-06-18 14:34 ` Catalin Marinas [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=20210618143401.GD16116@arm.com \
--to=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkovhaev@gmail.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).