From: Christoph Hellwig <hch@lst.de>
To: Arvind Sankar <nivedita@alum.mit.edu>
Cc: Lu Baolu <baolu.lu@linux.intel.com>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] iommu/vt-d: Return the correct dma mask when we are bypassing the IOMMU
Date: Thu, 17 Oct 2019 09:08:47 +0200 [thread overview]
Message-ID: <20191017070847.GA15037@lst.de> (raw)
In-Reply-To: <20191016191551.GA2692557@rani>
On Wed, Oct 16, 2019 at 03:15:52PM -0400, Arvind Sankar wrote:
> > > Reported-by: Arvind Sankar <nivedita@alum.mit.edu>
> > > Tested-by: Arvind Sankar <nivedita@alum.mit.edu>
> > > Originally-by: Christoph Hellwig <hch@lst.de>
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > Fixed-by: Arvind Sankar <nivedita@alum.mit.edu>
> > > Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
> >
> > This patch looks good to me.
> >
> > Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
> >
>
> Hi Christoph, will you be taking this through your dma-mapping branch?
Given this is a patch to intel-iommu I expect Joerg to pick it up.
But if he is fine with that I can also queue it up instead.
next prev parent reply other threads:[~2019-10-17 7:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 2:24 ehci-pci breakage with dma-mapping changes in 5.4-rc2 Arvind Sankar
2019-10-07 7:34 ` Christoph Hellwig
2019-10-07 17:54 ` Arvind Sankar
2019-10-07 17:55 ` Christoph Hellwig
2019-10-07 17:56 ` Christoph Hellwig
2019-10-07 17:58 ` Arvind Sankar
2019-10-07 18:32 ` Arvind Sankar
2019-10-07 18:47 ` Christoph Hellwig
2019-10-07 22:10 ` Arvind Sankar
2019-10-07 23:54 ` Arvind Sankar
2019-10-08 7:32 ` Christoph Hellwig
2019-10-08 11:51 ` Arvind Sankar
2019-10-08 12:50 ` Christoph Hellwig
2019-10-08 15:47 ` Arvind Sankar
2019-10-09 6:50 ` Christoph Hellwig
2019-10-09 13:48 ` Arvind Sankar
2019-10-08 7:29 ` Christoph Hellwig
2019-10-08 14:33 ` [PATCH] iommu/vt-d: Return the correct dma mask when we are bypassing the IOMMU Arvind Sankar
2019-10-09 2:45 ` Lu Baolu
2019-10-09 6:51 ` Christoph Hellwig
2019-10-10 1:24 ` Lu Baolu
2019-10-10 1:26 ` Lu Baolu
2019-10-16 19:15 ` Arvind Sankar
2019-10-17 7:08 ` Christoph Hellwig [this message]
2019-10-17 15:55 ` Arvind Sankar
2019-10-17 15:55 ` Arvind Sankar
2019-10-18 9:50 ` Joerg Roedel
2019-10-18 15:14 ` Christoph Hellwig
2019-10-18 15:21 ` Joerg Roedel
2019-10-18 15:22 ` Christoph Hellwig
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=20191017070847.GA15037@lst.de \
--to=hch@lst.de \
--cc=baolu.lu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nivedita@alum.mit.edu \
/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.