Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp771185imm; Thu, 31 May 2018 09:06:48 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI6vzb3fC93xt8anDwTUTt6FVSkY7dPDNJ/V9gltEEKV4F3MUFYMA6TxuRhEZHxFHzaDI3X X-Received: by 2002:aa7:8311:: with SMTP id t17-v6mr7432602pfm.45.1527782807977; Thu, 31 May 2018 09:06:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527782807; cv=none; d=google.com; s=arc-20160816; b=ZmFlBbiESY3v4KaUvo55j3NwQS3VlmIom7Y9cllVC7C6zF8ZtNkltl9+laUIcwaAvs ESkxSc1WvvUVbaJahtiXTJ4MKiI9ezj2HHNdn0IjoazCM+wIAtHjrPbOR6ENmQaSmAev /5M37yUdrB7qbioTR4NH5z5EqR8B61KvFNFdFKF6WoH9w/w+YQjJ+aeHEsVFibh496fM ILr1LnHbcHynDSvXDD1/AtdwCiofJL4ps05amyzlLemU3OjvfDKghoSPI6K3zaEugb7V J2icndSzPKz8fR5iP6V0q1n9yGxnNqzlWTbMfy8QSIbUHcHg7byx7TMbJQd9iwGxPjFE mw1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=DVukNfk2Wp+a7yTFWuDbYNOVWNTWOTZQimAVjYPflsw=; b=YNHvi2lDqq3U1Yzg87YyjllmhlqL87bXof9vjSM70ESXfkGG20TOoJjc3Xlxr6l4SM 1mpu9d8Yp5eJFLxP8436Uv0nsPKA3c+DGOnEefxI+ZHa4PkneOAxX1N4erV7kXR5Cu+v xWXP3ArymoQrfITMl4sDRQcRR5FoDWi54Jfy29iSZ06YCdu5bUTvYLa2+Eyu3awaGhOc rWY+KD850f2m86qtn1PnAntVFhUSYxhDl4uiGcvq0eB/qAemDvOY9vP7+grfLkxhQQcM GPxE71Nl3D3oCeX3tZD+V3ZjO1ave/V6JdCUY5BC5ozjUwXTYCcFjgPrtK4gOzM/aZG1 4L3A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=tp6U4nEz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p18-v6si29594937pgv.493.2018.05.31.09.06.33; Thu, 31 May 2018 09:06:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=tp6U4nEz; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755687AbeEaQEs (ORCPT + 99 others); Thu, 31 May 2018 12:04:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:59300 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755675AbeEaQEp (ORCPT ); Thu, 31 May 2018 12:04:45 -0400 Received: from localhost (li1825-44.members.linode.com [172.104.248.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CFC08208A5; Thu, 31 May 2018 16:04:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527782684; bh=PANfXzDziE/g8l48ykSUzyk6DA/Q6Zl4z/uuGN1I3+Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tp6U4nEzP2BuhelaWXy8TFsHijIhnS/LMqyViMM3u3wYw4qKQU2bLJ5hAaeqbRXn7 Jv6ke91cSU4cnv3dRhzkN7Ni1PFcbMJ2cpGEsEW75AAAmOzpLii5dHr8nFcSgCkgFV dPhUltGseoqowMvvhy+tqUJ5E/QmnTwQoBnQcaNA= Date: Thu, 31 May 2018 18:04:19 +0200 From: Greg Kroah-Hartman To: Timur Tabi Cc: Sebastian Gottschall , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Bjorn Andersson , Linus Walleij , Sasha Levin Subject: Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering Message-ID: <20180531160419.GA16172@kroah.com> References: <20180528100240.256525891@linuxfoundation.org> <20180528100302.722883806@linuxfoundation.org> <7c34ccef-2fa8-8b53-2677-29f6fbe71a04@dd-wrt.com> <20180531114553.GB11598@kroah.com> <510e5f2c-718a-de42-8274-9345d13e7797@codeaurora.org> <20180531121251.GA13561@kroah.com> <2898aafa-e185-8ad5-5f7f-9b81d4a36a8f@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2898aafa-e185-8ad5-5f7f-9b81d4a36a8f@codeaurora.org> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 31, 2018 at 10:09:50AM -0500, Timur Tabi wrote: > On 5/31/18 7:12 AM, Greg Kroah-Hartman wrote: > > Why is it somehow ok for "future" kernels? You can't break the api in > > the future for no reason. > > > > So this needs to be the same everywhere. If it is broken in 4.17-rc, it > > needs to be reverted. > > This was discussed here: > > https://www.spinics.net/lists/linux-arm-msm/msg32572.html > > The code can't program the value to 0 *and* support multiple TLMM devices at > the same time. Prior to 4.18, it is not possible to support multiple TLMMs > anyway, so blindly setting the base to -1 in the 4.17 kernel just breaks > existing user-space code that uses the legacy GPIO API. > > (This patch in 4.18 is what provides support for multiple TLMMs: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/pinctrl/qcom?id=f265e8b91bb50c7a732a171ddaeb0eef143bacd9) > > So you can see in the thread that I proposed a compromise: > > https://www.spinics.net/lists/linux-arm-msm/msg32596.html > > but that was rejected Ugh, ok, you all have fun with this :( I've reverted it from all of the stable trees, again, sorry for it coming back. greg k-h