[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180315175422.GE19870@char.us.oracle.com>
Date: Thu, 15 Mar 2018 13:54:22 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Christoph Hellwig <hch@....de>
Cc: x86@...nel.org, Tom Lendacky <thomas.lendacky@....com>,
David Woodhouse <dwmw2@...radead.org>,
Muli Ben-Yehuda <mulix@...ix.org>,
Jon Mason <jdmason@...zu.us>, Joerg Roedel <joro@...tes.org>,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 11/14] swiotlb: remove swiotlb_set_mem_attributes
On Thu, Mar 15, 2018 at 01:51:59PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Mar 14, 2018 at 06:52:10PM +0100, Christoph Hellwig wrote:
> > Now that set_memory_decrypted is always available we can just call it
> > directly.
> >
>
> Won't this break ARM build?
<brainfart> And of course right after asking that question I went back to
the previous patch as I had that in my mind it was arch/x86/include, not the global
one.
So pls ignore my query and instead:
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Powered by blists - more mailing lists