From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Mark Hounschell <markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Can't boot new 4.4 kernel with IOMMU enabled
Date: Tue, 16 Feb 2016 17:24:55 +0100 [thread overview]
Message-ID: <20160216162455.GX18805@8bytes.org> (raw)
In-Reply-To: <56B0CFF7.80907-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
On Tue, Feb 02, 2016 at 10:49:11AM -0500, Mark Hounschell wrote:
> Just wondering if this issue is still being considered?
Yes it is, I just went through a move and have a few other issues on the
plate. But I this is still on the list.
Joerg
next prev parent reply other threads:[~2016-02-16 16:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 21:37 Can't boot new 4.4 kernel with IOMMU enabled Mark Hounschell
[not found] ` <56957209.1080202-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-13 3:09 ` Baoquan He
[not found] ` <20160113030950.GB11902-0VdLhd/A9PlfpSRLqpFUpR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2016-01-13 14:42 ` Mark Hounschell
[not found] ` <56966244.80700-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-14 0:05 ` Baoquan He
[not found] ` <20160114000520.GA2449-ejN7fcUYdH/by3iVrkZq2A@public.gmane.org>
2016-01-14 14:04 ` Mark Hounschell
[not found] ` <5697AAD8.1000105-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-20 15:38 ` Joerg Roedel
[not found] ` <20160120153823.GG18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 15:46 ` Joerg Roedel
[not found] ` <20160120154658.GH18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 16:04 ` Mark Hounschell
[not found] ` <569FB013.4050709-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-20 16:19 ` Joerg Roedel
[not found] ` <20160120161904.GI18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 18:19 ` Mark Hounschell
[not found] ` <569FCFC8.2000606-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-20 18:26 ` Joerg Roedel
[not found] ` <20160120182602.GJ18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 19:32 ` Mark Hounschell
[not found] ` <569FE0B0.4030902-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-20 20:30 ` Joerg Roedel
2016-01-21 14:50 ` Mark Hounschell
[not found] ` <56A0F03C.8010109-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-21 14:58 ` Mark Hounschell
[not found] ` <56A0F221.10502-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-21 22:39 ` Joerg Roedel
[not found] ` <20160121223958.GL18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-02 15:49 ` Mark Hounschell
[not found] ` <56B0CFF7.80907-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-02-16 16:24 ` Joerg Roedel [this message]
[not found] ` <20160216162455.GX18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-16 17:32 ` Mark Hounschell
[not found] ` <56C35D1A.9080307-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-02-26 16:23 ` Joerg Roedel
[not found] ` <20160226162319.GH22747-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-26 19:20 ` Mark Hounschell
[not found] ` <56D0A565.8080406-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-02-29 17:42 ` Joerg Roedel
[not found] ` <20160229174252.GN22747-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-29 17:52 ` Mark Hounschell
[not found] ` <56D48560.4010904-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-03-18 17:24 ` Mark Hounschell
[not found] ` <56EC39CB.2010909-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-04-11 13:54 ` Joerg Roedel
[not found] ` <20160411135451.GO17838-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-04-11 14:59 ` Mark Hounschell
[not found] ` <570BBBE4.9040307-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-04-11 15:43 ` Joerg Roedel
2016-01-20 15:56 ` Mark Hounschell
2016-01-20 12:31 ` Joerg Roedel
[not found] ` <20160120123116.GF18805-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-01-20 13:03 ` Mark Hounschell
[not found] ` <569F858E.4060701-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-01-20 13:18 ` Baoquan He
2016-01-20 13:03 ` Baoquan He
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=20160216162455.GX18805@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=markh-n2QNKt385d+sTnJN9+BGXg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.