From: Daniel Walker <danielwa-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: "xe-kernel-qGaTmy9+pjmU+GOnkdjqUdBPR1lH4CV8@public.gmane.org"
<xe-kernel-qGaTmy9+pjmU+GOnkdjqUdBPR1lH4CV8@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
"Nikunj Kela (nkela)"
<nkela-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: Re: iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Wed, 15 Jun 2016 09:00:06 -0700 [thread overview]
Message-ID: <57617B86.6090205@cisco.com> (raw)
In-Reply-To: <20160615140529.GO26566-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On 06/15/2016 07:05 AM, Joerg Roedel wrote:
> On Tue, Jun 14, 2016 at 11:08:16AM -0700, Daniel Walker wrote:
>> I noticed that you responded to these changes saying they were applied to
>> your tree,
>>
>> https://lkml.org/lkml/2015/5/29/468
>>
>> but I haven't not seen them show up in mainline. Did they get removed for
>> some reason, or misplaced ? Or are they in mainline and I just missed them ?
> These patches turned out to be utterly broken. After writing more than
> 20 fixes for them, I was urged to re-write the stuff from scratch to get
> a clean history of the feature. So I dropped the patches from Li and
> queued my re-write instead.
>
>
> Joerg
>
That's surprising 11 versions and still broken ;( .. Can you point me
to your re-writes ?
Daniel
next prev parent reply other threads:[~2016-06-15 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 18:08 iommu/vt-d: Fix intel vt-d faults in kdump kernel Daniel Walker
[not found] ` <57604810.1070504-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2016-06-15 14:05 ` Joerg Roedel
[not found] ` <20160615140529.GO26566-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-06-15 16:00 ` Daniel Walker [this message]
[not found] ` <57617B86.6090205-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2016-06-15 16:13 ` Joerg Roedel
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=57617B86.6090205@cisco.com \
--to=danielwa-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=nkela-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=xe-kernel-qGaTmy9+pjmU+GOnkdjqUdBPR1lH4CV8@public.gmane.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;
as well as URLs for NNTP newsgroup(s).