From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] dma-debug: print some unfreed allocations
Date: Wed, 8 Jun 2011 14:37:58 +0200 [thread overview]
Message-ID: <20110608123758.GB21591@amd.com> (raw)
In-Reply-To: <1307536007.30277.0.camel@jlt3.sipsolutions.net>
On Wed, Jun 08, 2011 at 08:26:47AM -0400, Johannes Berg wrote:
> On Wed, 2011-06-08 at 14:16 +0200, Roedel, Joerg wrote:
>
> > > I see something similar was merged printing just the first one (and
> > > without stack trace it seems?). Are you still interested in this?
> >
> > Sure, still interested. The code which prints out the first entry has
> > been around for some time, its nothing new afaik.
>
> Ok. I was thinking of
> commit ba4b87ad5497cba555954885db99c99627f93748
> Author: Stanislaw Gruszka <sgruszka@redhat.com>
> Date: Thu Mar 31 08:08:09 2011 -0400
>
> dma-debug: print information about leaked entry
>
> which is fairly recent, recent enough that my original patch no longer
> applied anyway :-)
Ah, okay. I thought this change was older :-)
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2011-06-08 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 18:42 [PATCH] dma-debug: print some unfreed allocations Johannes Berg
2011-05-11 12:47 ` [PATCH v2] " Johannes Berg
2011-05-16 11:00 ` Roedel, Joerg
2011-05-18 22:48 ` Johannes Berg
2011-05-19 8:19 ` Roedel, Joerg
2011-05-20 16:36 ` [PATCH v3] " Johannes Berg
2011-05-23 12:35 ` Roedel, Joerg
2011-06-08 11:03 ` Johannes Berg
2011-06-08 12:16 ` Roedel, Joerg
2011-06-08 12:26 ` Johannes Berg
2011-06-08 12:37 ` Roedel, Joerg [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=20110608123758.GB21591@amd.com \
--to=joerg.roedel@amd.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.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