Hi Jordan,
On 05/02/18 18:15, Jordan Crouse wrote:
[...]
> Just a gentle nudge to see if there is any progress on this front. I know the
> last 6 months have been busy with other far more serious panics but I wanted
> to
> offer any help I could provide including testing on various qcom targets.
Hi Robin,
On 2/5/2018 11:38 PM, Robin Murphy wrote:
On 05/02/18 17:59, Vivek Gautam wrote:
Unmap returns a size_t all throughout the IOMMU framework.
Make io-pgtable match this convention.
Moreover, there isn't a need to have a signed int return type
as we return 0 in case of failures.
That
On Wed, Oct 25, 2017 at 02:20:15PM -0600, Jordan Crouse wrote:
> On Mon, Oct 23, 2017 at 02:00:07PM +0100, Jean-Philippe Brucker wrote:
> > Hi Jordan,
> >
> > [Lots of IOMMU people have been dropped from Cc, I've tried to add them
> > back]
> >
> > On 12/10/17 16:28, Jordan Crouse wrote:
> > >
On 05/02/18 17:59, Vivek Gautam wrote:
Unmap returns a size_t all throughout the IOMMU framework.
Make io-pgtable match this convention.
Moreover, there isn't a need to have a signed int return type
as we return 0 in case of failures.
That makes sense (the code itself has always followed that
Unmap returns a size_t all throughout the IOMMU framework.
Make io-pgtable match this convention.
Moreover, there isn't a need to have a signed int return type
as we return 0 in case of failures.
Signed-off-by: Vivek Gautam
---
drivers/iommu/io-pgtable-arm-v7s.c |
On 05/02/18 10:45, Suravee Suthikulpanit wrote:
Currently, iommu_unmap, iommu_unmap_fast and iommu_map_sg return
size_t. However, some of the return values are error codes (< 0),
which can be misinterpreted as large size. Therefore, returning size 0
instead to signify failure to map/unmap.
Cc:
Currently, iommu_unmap, iommu_unmap_fast and iommu_map_sg return
size_t. However, some of the return values are error codes (< 0),
which can be misinterpreted as large size. Therefore, returning size 0
instead to signify failure to map/unmap.
Cc: Joerg Roedel
Cc: Alex