From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f66.google.com ([74.125.82.66]:33945 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750922AbcEIG5F (ORCPT ); Mon, 9 May 2016 02:57:05 -0400 Received: by mail-wm0-f66.google.com with SMTP id n129so19058174wmn.1 for ; Sun, 08 May 2016 23:57:05 -0700 (PDT) Date: Mon, 9 May 2016 08:57:03 +0200 From: Daniel Vetter To: Lee Jones Cc: Daniel Vetter , Linus Walleij , Ville =?iso-8859-1?Q?Syrj=E4l=E4?= , Alexandre Courbot , Samuel Ortiz , Shobhit Kumar , intel-gfx , stable , "linux-gpio@vger.kernel.org" , Thierry Reding Subject: Re: [Intel-gfx] [PATCH] mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table correctly Message-ID: <20160509065703.GL27098@phenom.ffwll.local> References: <1461353935-8078-1-git-send-email-ville.syrjala@linux.intel.com> <20160502081938.GG14148@phenom.ffwll.local> <20160504073217.GB1503@dell.home> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160504073217.GB1503@dell.home> Sender: stable-owner@vger.kernel.org List-ID: On Wed, May 04, 2016 at 08:32:17AM +0100, Lee Jones wrote: > On Mon, 02 May 2016, Daniel Vetter wrote: > > > On Fri, Apr 29, 2016 at 11:31:44AM +0200, Linus Walleij wrote: > > > On Fri, Apr 22, 2016 at 9:38 PM, wrote: > > > > > > > From: Ville Syrj�l� > > > > > > > > GPIO lookup tables are supposed to be zero terminated. Let's do that > > > > and avoid accidentally walking off the end. > > > > > > > > Cc: Shobhit Kumar > > > > Cc: Samuel Ortiz > > > > Cc: Linus Walleij > > > > Cc: Alexandre Courbot > > > > Cc: Thierry Reding > > > > Cc: Lee Jones > > > > Cc: stable@vger.kernel.org > > > > Fixes: 61dd2ca2d44e ("mfd: intel_soc_pmic_core: Add lookup table for Panel Control as GPIO signal") > > > > Signed-off-by: Ville Syrj�l� > > > > > > Acked-by: Linus Walleij > > > > Applied to drm-intel trees, thanks for patch, reviews&acks. > > Do what now? How can you apply a patch for a subsystem you don't have > responsibility for? This is bound to cause merge conflicts. Oh crap, I thought Linus' ack was for the mfd stuff and didn't bother double-checking with MAINTAINTERS. Should I throw it out again and you'll pick it up, or ok as such? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch