On Sat, Mar 09, 2013 at 07:16:43PM +0100, Lars-Peter Clausen wrote:
> Currently i2c_del_adapter() returns 0 on success and potentially an error code
> on failure. Unfortunately this doesn't mix too well with the Linux device
> driver
> model. An i2c_adapter is usually registered in a drivers
On Sat, Mar 09, 2013 at 07:16:43PM +0100, Lars-Peter Clausen wrote:
Currently i2c_del_adapter() returns 0 on success and potentially an error code
on failure. Unfortunately this doesn't mix too well with the Linux device
driver
model. An i2c_adapter is usually registered in a drivers probe
On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
> Lars-Peter Clausen (6):
> i2c: Remove detach_adapter
> i2c: i2c_del_adapter: Don't treat removing a non-registered adapter
> as error
> i2c: Ignore return value of i2c_del_adapter()
> i2c: Make return type of
On Sat, 30 Mar 2013 21:43:29 +0100, Lars-Peter Clausen wrote:
> On 03/30/2013 09:13 PM, Jean Delvare wrote:
> > I see:
> >
> > struct device_driver {
> > (...)
> > int (*probe) (struct device *dev);
> > int (*remove) (struct device *dev);
> >
> > So the driver core does allow remove
On Sat, 30 Mar 2013 21:43:29 +0100, Lars-Peter Clausen wrote:
On 03/30/2013 09:13 PM, Jean Delvare wrote:
I see:
struct device_driver {
(...)
int (*probe) (struct device *dev);
int (*remove) (struct device *dev);
So the driver core does allow remove functions to
On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
Lars-Peter Clausen (6):
i2c: Remove detach_adapter
i2c: i2c_del_adapter: Don't treat removing a non-registered adapter
as error
i2c: Ignore return value of i2c_del_adapter()
i2c: Make return type of i2c_del_adapter()
On 03/30/2013 09:13 PM, Jean Delvare wrote:
> Hi Lars,
>
> On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
>> Currently i2c_del_adapter() returns 0 on success and potentially an error
>> code
>> on failure. Unfortunately this doesn't mix too well with the Linux device
>> driver
>>
Hi Lars,
On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
> Currently i2c_del_adapter() returns 0 on success and potentially an error code
> on failure. Unfortunately this doesn't mix too well with the Linux device
> driver
> model. (...)
I see:
struct device_driver {
On Sat, Mar 09, 2013 at 07:16:43PM +0100, Lars-Peter Clausen wrote:
> Currently i2c_del_adapter() returns 0 on success and potentially an error code
> on failure. Unfortunately this doesn't mix too well with the Linux device
> driver
> model. An i2c_adapter is usually registered in a drivers
On Sat, Mar 09, 2013 at 07:16:43PM +0100, Lars-Peter Clausen wrote:
Currently i2c_del_adapter() returns 0 on success and potentially an error code
on failure. Unfortunately this doesn't mix too well with the Linux device
driver
model. An i2c_adapter is usually registered in a drivers probe
Hi Lars,
On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
Currently i2c_del_adapter() returns 0 on success and potentially an error code
on failure. Unfortunately this doesn't mix too well with the Linux device
driver
model. (...)
I see:
struct device_driver {
(...)
On 03/30/2013 09:13 PM, Jean Delvare wrote:
Hi Lars,
On Sat, 9 Mar 2013 19:16:43 +0100, Lars-Peter Clausen wrote:
Currently i2c_del_adapter() returns 0 on success and potentially an error
code
on failure. Unfortunately this doesn't mix too well with the Linux device
driver
model. (...)
Currently i2c_del_adapter() returns 0 on success and potentially an error code
on failure. Unfortunately this doesn't mix too well with the Linux device driver
model. An i2c_adapter is usually registered in a drivers probe callback and
removed in the drivers remove callback. The Linux device
Currently i2c_del_adapter() returns 0 on success and potentially an error code
on failure. Unfortunately this doesn't mix too well with the Linux device driver
model. An i2c_adapter is usually registered in a drivers probe callback and
removed in the drivers remove callback. The Linux device
14 matches
Mail list logo