On 1/16/19 11:16 AM, Jerome Glisse wrote: >> We also rework the old error message a bit since we do not get >> the conflicting entry back: only an indication that we *had* a >> conflict. > We should keep the device private check (moving it in __request_region) > as device private can try to register un-use physical address (un-use > at time of device private registration) that latter can block valid > physical address the error message you are removing report such event. If a resource can't support having a child, shouldn't it just be marked IORESOURCE_BUSY, rather than trying to somehow special-case IORES_DESC_DEVICE_PRIVATE_MEMORY behavior?
