From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Myron Stowe <myron.stowe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Don Brace <don.brace-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>,
Joseph Szczypek
<jszczype-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH v3] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped
Date: Tue, 3 Jan 2017 17:11:27 +0100 [thread overview]
Message-ID: <20170103161127.GI17255@8bytes.org> (raw)
In-Reply-To: <CAL-B5D0JFx678Y-zMoQVXBrqt0TajvcpEKn1emnoCQtYaK=DZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Jan 03, 2017 at 08:23:23AM -0700, Myron Stowe wrote:
> This didn't seem to make the 4.10 merge window. Was that on purpose?
> Any idea when you might include this in a pull request for Linus?
I will collect fixes this week and send them to Linus, they will also
include this patch.
Joerg
next prev parent reply other threads:[~2017-01-03 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:09 [PATCH v3] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped Xunlei Pang
2016-12-06 16:03 ` Joerg Roedel
[not found] ` <20161206160346.GB27203-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-01-03 15:23 ` Myron Stowe
[not found] ` <CAL-B5D0JFx678Y-zMoQVXBrqt0TajvcpEKn1emnoCQtYaK=DZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-03 16:11 ` Joerg Roedel [this message]
[not found] ` <1480939747-31916-1-git-send-email-xlpang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-06 22:03 ` Don Brace
2017-01-04 14:14 ` 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=20170103161127.GI17255@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=don.brace-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jszczype-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=myron.stowe-Re5JQEeQqe8AvxtiuMwx3w@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