linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	reinette.chatre@intel.com, benh@kernel.crashing.org
Subject: Re: dma-debug: add a check dma memory leaks
Date: Sun, 10 May 2009 09:49:39 +0100	[thread overview]
Message-ID: <1241945379.24436.130.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090510020911.GA4722@kroah.com>

On Sat, 2009-05-09 at 19:09 -0700, Greg KH wrote:
> On Sun, May 10, 2009 at 12:59:12AM +0100, David Woodhouse wrote:
> > Subject: Add BUS_NOTIFY_UNBOUND_DRIVER callback after driver removal
> > 
> > This adds a notifier callback which happens _after_ the driver has been
> > unbound from the device, needed for things like the DMA debugging API
> > which want to check that all DMA mappings have been correctly torn down.
> > 
> > Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
> 
> I don't understand.  Who wrote this patch, Joerg or you?  I have this in
> my tree already as written by Joerg.

In that case we probably both did it, independently. I did it last night
after finally catching up with Ben and talking about the possibility of
moving the existing notifiers. Jörg may have done it sooner.

You can drop my version, then.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


  reply	other threads:[~2009-05-10  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903302101.n2UL1O1n011970@hera.kernel.org>
2009-04-17 21:51 ` dma-debug: add a check dma memory leaks David Woodhouse
2009-04-21  9:20   ` Joerg Roedel
2009-05-09 23:59     ` David Woodhouse
2009-05-10  1:46       ` Benjamin Herrenschmidt
2009-05-10  2:09       ` Greg KH
2009-05-10  8:49         ` David Woodhouse [this message]
2009-05-10  9:32           ` Benjamin Herrenschmidt
2009-05-11 17:43             ` Greg KH

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=1241945379.24436.130.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reinette.chatre@intel.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).