From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joerg.roedel@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
reinette.chatre@intel.com
Subject: Re: dma-debug: add a check dma memory leaks
Date: Mon, 11 May 2009 10:43:01 -0700 [thread overview]
Message-ID: <20090511174301.GC4534@kroah.com> (raw)
In-Reply-To: <1241947932.19955.10.camel@pasglop>
On Sun, May 10, 2009 at 07:32:12PM +1000, Benjamin Herrenschmidt wrote:
> On Sun, 2009-05-10 at 09:49 +0100, David Woodhouse wrote:
> > > 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.
>
> As long as it's strictly identical :-) IE. I don't want to -move- the
> existing notifier, but adding a "BOUND" one is fine.
Look in the linux-next tree to verify that it is the same.
Or here's a direct link to the patch:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-driver-core/driver-core-add-bus_notify_unbound_driver-event.patch
thanks,
greg k-h
prev parent reply other threads:[~2009-05-11 17:56 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 ` 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
2009-05-10 9:32 ` Benjamin Herrenschmidt
2009-05-11 17:43 ` Greg KH [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=20090511174301.GC4534@kroah.com \
--to=greg@kroah.com \
--cc=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--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
Powered by JetHome