Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Thu, Sep 22, 2016 at 10:59:24AM +0200, Wolfram Sang wrote: > > > > Huh? It doesn't apply on top of rc7 here? What did you base it on? > > > > It is based on linux-next as it is on top of Jarkko's I2C ACPI namespace > > cleanup patches. I'm wondering if I make an updated patch on top of > >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Thu, Sep 22, 2016 at 10:59:24AM +0200, Wolfram Sang wrote: > > > > Huh? It doesn't apply on top of rc7 here? What did you base it on? > > > > It is based on linux-next as it is on top of Jarkko's I2C ACPI namespace > > cleanup patches. I'm wondering if I make an updated patch on top of > >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

> > Huh? It doesn't apply on top of rc7 here? What did you base it on? > > It is based on linux-next as it is on top of Jarkko's I2C ACPI namespace > cleanup patches. I'm wondering if I make an updated patch on top of > v4.8-rc7 does it conflict with the I2C stuff in linux-next? What's your >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

> > Huh? It doesn't apply on top of rc7 here? What did you base it on? > > It is based on linux-next as it is on top of Jarkko's I2C ACPI namespace > cleanup patches. I'm wondering if I make an updated patch on top of > v4.8-rc7 does it conflict with the I2C stuff in linux-next? What's your >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 06:14:38PM +0200, Wolfram Sang wrote: > On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote: > > On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > > > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > > > When enumerating I2C

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 06:14:38PM +0200, Wolfram Sang wrote: > On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote: > > On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > > > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > > > When enumerating I2C

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote: > On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > > When enumerating I2C devices connected to an I2C adapter we scan the whole > > > namespace (as

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote: > On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > > When enumerating I2C devices connected to an I2C adapter we scan the whole > > > namespace (as

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > When enumerating I2C devices connected to an I2C adapter we scan the whole > > namespace (as it is possible to have devices anywhere in that namespace, > > not just

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote: > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > > When enumerating I2C devices connected to an I2C adapter we scan the whole > > namespace (as it is possible to have devices anywhere in that namespace, > > not just

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C >

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

Mika Westerberg writes: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C > bus in

Re: [PATCH v2] i2c / ACPI: Do not touch an I2C device if it belongs to another adapter

Mika Westerberg writes: > When enumerating I2C devices connected to an I2C adapter we scan the whole > namespace (as it is possible to have devices anywhere in that namespace, > not just below the I2C adapter device) and add each found device to the I2C > bus in question. > > Now after commit