From: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] iommu/vt-d: Make sure IOMMUs are off when intel_iommu=off
Date: Thu, 13 Apr 2017 06:57:50 +0800 [thread overview]
Message-ID: <20170412225750.GA28936@x1> (raw)
In-Reply-To: <20170412215408.GF7266-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On 04/12/17 at 11:54pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> > Do you plan to merge this one as urgent?
> >
> > There's bug created about this issue on rhel, it would be great if it
> > can be put in next or merged so that we can back port it.
>
> No, I am not sending this for v4.11, because this issue existed forever
> and is no regression. I queued it for v4.12 and the commit-id in the
> iommu-tree will be the same as upstream, if you need that for your
> backport.
Yeah, agree. The commit-id should be enough. Thanks a lot!
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, Joerg Roedel <jroedel@suse.de>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Make sure IOMMUs are off when intel_iommu=off
Date: Thu, 13 Apr 2017 06:57:50 +0800 [thread overview]
Message-ID: <20170412225750.GA28936@x1> (raw)
In-Reply-To: <20170412215408.GF7266@8bytes.org>
On 04/12/17 at 11:54pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> > Do you plan to merge this one as urgent?
> >
> > There's bug created about this issue on rhel, it would be great if it
> > can be put in next or merged so that we can back port it.
>
> No, I am not sending this for v4.11, because this issue existed forever
> and is no regression. I queued it for v4.12 and the commit-id in the
> iommu-tree will be the same as upstream, if you need that for your
> backport.
Yeah, agree. The commit-id should be enough. Thanks a lot!
next prev parent reply other threads:[~2017-04-12 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 15:00 [PATCH] iommu/vt-d: Make sure IOMMUs are off when intel_iommu=off Joerg Roedel
2017-03-29 15:00 ` Joerg Roedel
[not found] ` <1490799639-15965-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-03-29 15:51 ` Jacob Pan
2017-03-29 15:51 ` Jacob Pan
2017-03-29 21:01 ` Joerg Roedel
2017-03-29 21:01 ` Joerg Roedel
2017-04-12 1:40 ` Baoquan He
2017-04-12 1:40 ` Baoquan He
2017-04-12 21:54 ` Joerg Roedel
2017-04-12 21:54 ` Joerg Roedel
[not found] ` <20170412215408.GF7266-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-04-12 22:57 ` Baoquan He [this message]
2017-04-12 22:57 ` 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=20170412225750.GA28936@x1 \
--to=bhe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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.