From: Catalin Marinas <catalin.marinas@arm.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: clear cfg80211_inform_bss() from kmemleak reports
Date: Fri, 04 Sep 2009 23:24:27 +0100 [thread overview]
Message-ID: <1252103067.21380.1.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <43e72e890909041458u505ce89tf38743dd6305bf7b@mail.gmail.com>
On Fri, 2009-09-04 at 14:58 -0700, Luis R. Rodriguez wrote:
> On Fri, Sep 4, 2009 at 2:21 PM, Luis R. Rodriguez<lrodriguez@atheros.com> wrote:
>
> > BTW I should not I got this kmemleak report after using the clear
> > command by painting objects black. I'll test it now with your
> > suggested changes.
>
> So I pulled your git://linux-arm.org/linux-2.6 master into my tree and
> didn't even need a 'clear' command now, the output of
> /sys/kernel/debug/kmemleak is empty :), so I suspect you have quite a
> few changes which should help avoid getting false positives.
>
> Will these changes make it for 2.6.32?
The kmemleak branch is planned for the upcoming merging window. I don't
think you need to merge the master branch as it has a lot of
arm-specific code.
--
Catalin
next prev parent reply other threads:[~2009-09-04 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251958266-10692-1-git-send-email-lrodriguez@atheros.com>
[not found] ` <1251962791.3336.3.camel@johannes.local>
2009-09-03 18:13 ` Luis R. Rodriguez
2009-09-03 18:17 ` Johannes Berg
2009-09-03 20:43 ` Luis R. Rodriguez
2009-09-04 5:04 ` Johannes Berg
2009-09-04 8:25 ` Catalin Marinas
2009-09-04 21:21 ` Luis R. Rodriguez
2009-09-04 21:41 ` Luis R. Rodriguez
2009-09-04 21:58 ` Luis R. Rodriguez
2009-09-04 22:24 ` Catalin Marinas [this message]
2009-09-04 22:48 ` Luis R. Rodriguez
2009-09-05 0:03 ` Luis R. Rodriguez
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=1252103067.21380.1.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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®