RE: [PATCH v4 5/6] iommu: Use EINVAL for incompatible device/domain in ->attach_dev

From: Tian, Kevin
Date: Thu Sep 22 2022 - 04:20:33 EST

Next message: Adrian Hunter: "Re: [PATCH v2] mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake"
Previous message: kernel test robot: "drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces)"
In reply to: Baolu Lu: "Re: [PATCH v4 5/6] iommu: Use EINVAL for incompatible device/domain in ->attach_dev"
Next in thread: Nicolin Chen: "[PATCH v4 6/6] iommu: Propagate return value in ->attach_dev callback functions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> From: Nicolin Chen <nicolinc@xxxxxxxxxx>
> Sent: Wednesday, September 21, 2022 4:24 PM
>
> Following the new rules in include/linux/iommu.h kdocs, update all drivers
> ->attach_dev callback functions to return EINVAL in the failure paths that
> are related to domain incompatibility.
>
> Also, drop adjacent error prints to prevent a kernel log spam.
>
> Signed-off-by: Nicolin Chen <nicolinc@xxxxxxxxxx>

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

Next message: Adrian Hunter: "Re: [PATCH v2] mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake"
Previous message: kernel test robot: "drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces)"
In reply to: Baolu Lu: "Re: [PATCH v4 5/6] iommu: Use EINVAL for incompatible device/domain in ->attach_dev"
Next in thread: Nicolin Chen: "[PATCH v4 6/6] iommu: Propagate return value in ->attach_dev callback functions"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]