From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] kmemleak: fix sparse warning for static declarations
Date: Thu, 3 Sep 2009 09:17:13 +0300 [thread overview]
Message-ID: <84144f020909022317m776bbf86xe523144451f97693@mail.gmail.com> (raw)
In-Reply-To: <1251942059-21448-6-git-send-email-lrodriguez@atheros.com>
On Thu, Sep 3, 2009 at 4:40 AM, Luis R. Rodriguez<lrodriguez@atheros.com> wrote:
> This fixes these sparse warnings:
>
> mm/kmemleak.c:1179:6: warning: symbol 'start_scan_thread' was not declared. Should it be static?
> mm/kmemleak.c:1194:6: warning: symbol 'stop_scan_thread' was not declared. Should it be static?
>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
prev parent reply other threads:[~2009-09-03 6:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 1:40 [PATCH 0/5] kmemleak: few small cleanups and clear command support Luis R. Rodriguez
2009-09-03 1:40 ` [PATCH 1/5] kmemleak: use bool for true/false questions Luis R. Rodriguez
2009-09-03 6:02 ` Pekka Enberg
2009-09-03 1:40 ` [PATCH 2/5] kmemleak: add clear command support Luis R. Rodriguez
2009-09-03 1:40 ` [PATCH 3/5] kmemleak: move common painting code together Luis R. Rodriguez
2009-09-03 6:03 ` Pekka Enberg
2009-09-03 1:40 ` [PATCH 4/5] kmemleak: fix sparse warning over overshadowed flags Luis R. Rodriguez
2009-09-03 6:16 ` Pekka Enberg
2009-09-03 1:40 ` [PATCH 5/5] kmemleak: fix sparse warning for static declarations Luis R. Rodriguez
2009-09-03 6:17 ` Pekka Enberg [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=84144f020909022317m776bbf86xe523144451f97693@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.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
all inboxes | Powered by JetHome®