From: Joerg Roedel <joro@8bytes.org>
To: Greg KH <gregkh@suse.de>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver/base: add BUS_NOTIFY_UNBOUND_DRIVER event
Date: Sat, 25 Apr 2009 01:24:47 +0200 [thread overview]
Message-ID: <20090424232447.GB12658@8bytes.org> (raw)
In-Reply-To: <20090424184425.GB20845@suse.de>
On Fri, Apr 24, 2009 at 11:44:25AM -0700, Greg KH wrote:
> On Fri, Apr 24, 2009 at 02:57:00PM +0200, Joerg Roedel wrote:
> > This patch adds a new bus notifier event which is emitted _after_ a
> > device is removed from its driver. This event will be used by the
> > dma-api debug code to check if a driver has released all dma allocations
> > for that device.
>
> Heh, I was wondering if people were going to need that. I'll queue it
> up for 2.6.31, is that ok with you? Do you have patches that depend on
> it?
2.6.31 is ok for me. I sent Ingo a patch to remove the broken feature
which uses the wrong event for 2.6.30. I can reintroduce the fixed
version for 2.6.31 too.
Other way may be to send this patch to 2.6.30 which makes a smaller fix
possible for dma-api debugging. But I am not sure if this new event
could go in after the merge window. So I choosed this way :)
For me, 2.6.31 for this patch is fine.
Thanks,
Joerg
next prev parent reply other threads:[~2009-04-24 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 12:57 [PATCH] driver/base: add BUS_NOTIFY_UNBOUND_DRIVER event Joerg Roedel
2009-04-24 18:44 ` Greg KH
2009-04-24 23:24 ` Joerg Roedel [this message]
2009-04-24 23:44 ` 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=20090424232447.GB12658@8bytes.org \
--to=joro@8bytes.org \
--cc=gregkh@suse.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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