On Wed, Jan 14, 2015 at 04:18:56PM +0200, Pantelis Antoniou wrote: > Hi Guenter, > > > On Jan 14, 2015, at 16:14 , Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > > > > On 01/14/2015 05:54 AM, Pantelis Antoniou wrote: > > > >>> That being said, nobody complained about this in 11 years, so I would > >>> be surprised if it was plain wrong. I'd rather question the test code. > >>> Where is it? > >>> > >> > >> No-one has apparently tested removing an i2c mux device on a running system > >> before. > >> > > Hi Pantelis, > > > > We didn't see the problem with 3.14. That was with an earlier version of the > > overlay patchset, though. > > > > There have been changes to the overlay patchset since then true, but I don’t see > how that would trigger a deadlock in i2c. The completion wait just seems bogus to me. > Maybe the problem is triggered by a change in the infrastructure. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
