From: David Woodhouse <dwmw2@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Chris Wright <chrisw@sous-sol.org>, kvm <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH v2] intel-iommu: Fix use after release during device attach
Date: Thu, 21 Apr 2011 16:42:58 +0100 [thread overview]
Message-ID: <1303400579.23521.2.camel@i7.infradead.org> (raw)
In-Reply-To: <1303396097.3050.4.camel@x201>
On Thu, 2011-04-21 at 15:28 +0100, Alex Williamson wrote:
> I've been wondering the exact same thing. My last patch took weeks of
> prodding, finally went into the maintainer's tree without
> acknowledgment, and there's hardly been any activity there to suggest
> a pull request for 2.6.39 is going to happen. David, are you still
> interested in maintaining this code? Thanks,
Yes, sorry, I've been somewhat snowed under with various things.
This patch has been in my tree for a while, and I've just merged one
more patch which is outstanding and sent Linus a pull request.
--
dwmw2
next prev parent reply other threads:[~2011-04-21 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 7:05 [PATCH] intel-iommu: Fix use after release during device attach Jan Kiszka
2010-11-02 7:31 ` Sheng Yang
2010-11-02 7:46 ` Jan Kiszka
2010-11-02 7:57 ` Sheng Yang
2010-11-02 8:00 ` Sheng Yang
2010-11-14 9:18 ` Jan Kiszka
2010-12-10 8:36 ` Jan Kiszka
2010-12-10 18:44 ` Chris Wright
2011-01-04 10:42 ` Jan Kiszka
2011-04-21 12:32 ` [PATCH v2] " Jan Kiszka
2011-04-21 14:02 ` Chris Wright
2011-04-21 14:28 ` Alex Williamson
2011-04-21 15:42 ` David Woodhouse [this message]
2011-04-21 16:14 ` Alex Williamson
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=1303400579.23521.2.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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;
as well as URLs for NNTP newsgroup(s).