From: Joerg Roedel <joro@8bytes.org>
To: Nadav Amit <namit@vmware.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Logan Gunthorpe <logang@deltatee.com>,
David Woodhouse <dwmw2@infradead.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH] iommu/vt-d: Fix wrong analysis whether devices share the same bus
Date: Fri, 30 Aug 2019 15:48:00 +0200 [thread overview]
Message-ID: <20190830134800.GA11578@8bytes.org> (raw)
In-Reply-To: <20190820085317.29458-1-namit@vmware.com>
On Tue, Aug 20, 2019 at 01:53:17AM -0700, Nadav Amit wrote:
> drivers/iommu/intel_irq_remapping.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2019-08-30 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 8:53 [PATCH] iommu/vt-d: Fix wrong analysis whether devices share the same bus Nadav Amit
2019-08-23 23:06 ` Logan Gunthorpe
2019-08-30 13:48 ` Joerg Roedel [this message]
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=20190830134800.GA11578@8bytes.org \
--to=joro@8bytes.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=namit@vmware.com \
--cc=stable@vger.kernel.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).