Re: [PATCH v5 05/15] i2c: acpi: Return error pointers from i2c_acpi_new_device()

2018-11-30 Thread Wolfram Sang
On Wed, Nov 28, 2018 at 01:45:25PM +0200, Andy Shevchenko wrote: > The caller would like to know the reason why the i2c_acpi_new_device() fails. > For example, if adapter is not available, it might be in the future and we > would like to re-probe the clients again. But at the same time we would lik

Re: [PATCH v5 05/15] i2c: acpi: Return error pointers from i2c_acpi_new_device()

2018-11-28 Thread Mika Westerberg
On Wed, Nov 28, 2018 at 01:45:25PM +0200, Andy Shevchenko wrote: > The caller would like to know the reason why the i2c_acpi_new_device() fails. > For example, if adapter is not available, it might be in the future and we > would like to re-probe the clients again. But at the same time we would lik

[PATCH v5 05/15] i2c: acpi: Return error pointers from i2c_acpi_new_device()

2018-11-28 Thread Andy Shevchenko
The caller would like to know the reason why the i2c_acpi_new_device() fails. For example, if adapter is not available, it might be in the future and we would like to re-probe the clients again. But at the same time we would like to bail out if the error seems unrecoverable, such as invalid argumen