[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181127134623.GR10650@smile.fi.intel.com>
Date: Tue, 27 Nov 2018 15:46:23 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Hans de Goede <hdegoede@...hat.com>,
Darren Hart <dvhart@...radead.org>,
platform-driver-x86@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-acpi@...r.kernel.org, Jonathan Cameron <jic23@...nel.org>,
Wolfram Sang <wsa@...-dreams.de>, linux-i2c@...r.kernel.org,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 05/13] i2c: acpi: Return error pointers from
i2c_acpi_new_device()
On Tue, Nov 27, 2018 at 01:49:53PM +0200, Mika Westerberg wrote:
> On Tue, Nov 27, 2018 at 10:16:25AM +0100, Hans de Goede wrote:
> > One problem is that i2c_new_device() currently simply returns NULL on all
> > errors. Andy, you could take a look how much work it is to make that return
> > an ERR_PTR too, or just check its return value and return ERR_PTR(-ENXIO) if
> > it fails for now...
>
> I would use -ENODEV here and -EINVAL in case there is no ACPI companion :)
Sounds more traditional than ENXIO.
I would go the way Mika proposed if there is no objection.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists