From: Randy Dunlap <rdunlap@infradead.org>
To: Rahul Bedarkar <rahulbedarkar89@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] Documentation: kmemleak: correct spelling mistake
Date: Tue, 12 Aug 2014 09:42:34 -0700 [thread overview]
Message-ID: <53EA43FA.2040006@infradead.org> (raw)
In-Reply-To: <1406830819-7661-1-git-send-email-rahulbedarkar89@gmail.com>
On 07/31/14 11:20, Rahul Bedarkar wrote:
> Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Jiri, please add to trivial. Thanks.
> ---
> Documentation/kmemleak.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
> index b772418..f4f033c 100644
> --- a/Documentation/kmemleak.txt
> +++ b/Documentation/kmemleak.txt
> @@ -122,7 +122,7 @@ Then as usual to get your report with:
> Freeing kmemleak internal objects
> ---------------------------------
>
> -To allow access to previosuly found memory leaks after kmemleak has been
> +To allow access to previously found memory leaks after kmemleak has been
> disabled by the user or due to an fatal error, internal kmemleak objects
> won't be freed when kmemleak is disabled, and those objects may occupy
> a large part of physical memory.
>
--
~Randy
prev parent reply other threads:[~2014-08-12 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 18:20 [PATCH] Documentation: kmemleak: correct spelling mistake Rahul Bedarkar
2014-08-12 16:42 ` Randy Dunlap [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=53EA43FA.2040006@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rahulbedarkar89@gmail.com \
--cc=trivial@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