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

Hi, On 27-11-18 20:27, Andy Shevchenko wrote: On Tue, Nov 27, 2018 at 05:14:06PM +0100, Hans de Goede wrote: On 27-11-18 16:37, 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

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

Hi, On 27-11-18 20:27, Andy Shevchenko wrote: On Tue, Nov 27, 2018 at 05:14:06PM +0100, Hans de Goede wrote: On 27-11-18 16:37, 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

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

On Tue, Nov 27, 2018 at 05:14:06PM +0100, Hans de Goede wrote: > On 27-11-18 16:37, 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: [PATCH v3 05/13] i2c: acpi: Return error pointers from i2c_acpi_new_device()

On Tue, Nov 27, 2018 at 05:14:06PM +0100, Hans de Goede wrote: > On 27-11-18 16:37, 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: [PATCH v3 05/13] i2c: acpi: Return error pointers from i2c_acpi_new_device()

Hi, On 27-11-18 17:14, Hans de Goede wrote: Hi, On 27-11-18 16:37, 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

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

Hi, On 27-11-18 17:14, Hans de Goede wrote: Hi, On 27-11-18 16:37, 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

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

Hi, On 27-11-18 16:37, 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 like to bail out if the

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

Hi, On 27-11-18 16:37, 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 like to bail out if the

[PATCH v3 05/13] i2c: acpi: Return error pointers from i2c_acpi_new_device()

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

[PATCH v3 05/13] i2c: acpi: Return error pointers from i2c_acpi_new_device()

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