From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752986AbcEAV0o (ORCPT ); Sun, 1 May 2016 17:26:44 -0400 Received: from saturn.retrosnub.co.uk ([178.18.118.26]:48866 "EHLO saturn.retrosnub.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752921AbcEAV0m (ORCPT ); Sun, 1 May 2016 17:26:42 -0400 Subject: Re: Regression in inv_mpu6050: 4.6.0-rc5 To: One Thousand Gnomes , Michael Welling References: <20160426232651.099a18d7@lxorguk.ukuu.org.uk> <20160426230755.GA6235@deathstar> <20160427165613.4d464792@lxorguk.ukuu.org.uk> Cc: linux-kernel@vger.kernel.org, mranostay@gmail.com, daniel.baluta@intel.com, linux-iio@vger.kernel.org From: Jonathan Cameron Message-ID: Date: Sun, 1 May 2016 20:58:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160427165613.4d464792@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27/04/16 16:56, One Thousand Gnomes wrote: > On Tue, 26 Apr 2016 18:07:55 -0500 > Michael Welling wrote: > >> On Tue, Apr 26, 2016 at 11:26:51PM +0100, One Thousand Gnomes wrote: >>> >>> This now causes us to crash and burn on the ASUS T100TA Baytrail/T >>> platforms >>> >> >> I believe this regression has already been patched. >> >> Check the latest commits in linux-next. >> >> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c >> >> See if the latest patches fix your issue. > > It does - as this is a regression can we please get those fixes into the > next -rc ? > I'm afraid I'm lost in this one - which patch caused the regression and which one fixed it? The only patches I can immediately see in next both introduce and then squish a similar bug, but neither of them has hit Linus' tree yet. Or are we dealing with what was fixed in: c816d9e7 iio: imu: mpu6050: fix possible NULL dereferences I had understood that one as more hypothetical than real... Unfortunately I'm travelling and I suspect that means this will only get in just after the release (so for 4.6.1) once I've confirmed which fixes we actually need to backport. Jonathan