[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181212110435.GC1990@kroah.com>
Date: Wed, 12 Dec 2018 12:04:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Joerg Roedel <joro@...tes.org>
Cc: iommu@...ts.linux-foundation.org,
Russell Currey <ruscur@...sell.cc>,
Sam Bobroff <sbobroff@...ux.ibm.com>, oohall@...il.com,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Hanjun Guo <hanjun.guo@...aro.org>,
Sudeep Holla <sudeep.holla@....com>,
Dan Williams <dan.j.williams@...el.com>,
Vinod Koul <vkoul@...nel.org>, jroedel@...e.de,
Mathias Nyman <mathias.nyman@...el.com>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
dmaengine@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 1/6] driver core: Introduce device_iommu_mapped() function
On Tue, Dec 11, 2018 at 02:43:38PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@...e.de>
>
> Some places in the kernel check the iommu_group pointer in
> 'struct device' in order to find ot whether a device is
> mapped by an IOMMU.
>
> This is not good way to make this check, as the pointer will
> be moved to 'struct dev_iommu_data'. This way to make the
> check is also not very readable.
>
> Introduce an explicit function to perform this check.
>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
No need to have a cc: line if I have already acked it :)
thanks,
greg k-h
Powered by blists - more mailing lists