From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines Date: Wed, 4 Jan 2017 19:50:29 +0100 Message-ID: <20170104195029.0b7c660d@endymion> References: <1482843136-12838-1-git-send-email-pali.rohar@gmail.com> <201701032105.51144@pali> <20170103202418.GE16032@dtor-ws> <201701032139.13061@pali> <20170103205937.GA2289@dtor-ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <20170103205937.GA2289@dtor-ws> Sender: linux-kernel-owner@vger.kernel.org To: Dmitry Torokhov Cc: Pali =?UTF-8?B?Um9ow6Fy?= , Benjamin Tissoires , =?UTF-8?B?TWljaGHFgiBLxJlwaWXFhA==?= , Wolfram Sang , Steven Honeyman , Valdis.Kletnieks@vt.edu, Jochen Eisinger , Gabriele Mazzotta , Andy Lutomirski , Mario_Limonciello@dell.com, Alex Hung , Takashi Iwai , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Tue, 3 Jan 2017 12:59:37 -0800, Dmitry Torokhov wrote: > On Tue, Jan 03, 2017 at 09:39:13PM +0100, Pali Rohár wrote: > > Some distributions blacklist i2c-i801.ko module... And > > Any particular reason for that? At some point in time, the i2c-i801 driver caused problems on a few systems. They decided that blacklisting the driver for everybody was the easiest way to fix the problem. Of course this doesn't make any sense and should be reverted. The root cause of the problem should have been investigated back then. Maybe it's fixed by now and they will never now... -- Jean Delvare SUSE L3 Support