Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1212626ybg; Thu, 4 Jun 2020 04:08:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw86/OqcqoSH6pFktvAgFRwezD5KY3WpceWAD+TNPfL7pQburMmCt9mwMlLfSCri8fZeSQP X-Received: by 2002:a17:906:5652:: with SMTP id v18mr3278250ejr.72.1591268910303; Thu, 04 Jun 2020 04:08:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591268910; cv=none; d=google.com; s=arc-20160816; b=ycJo1/T5eJh9bp2jlsJ2v0BI2fzgmdQ1TWdfOKHf0WTLjKJMVq7xXuVGI4HZ9Plcix LJoS2QLCI15qjQKMW7Xf4lNDOzmKhkxwQ+j8/1tJrCZUJXgpyNimKe0NgCN6818WrGSg /TuWWsP38PzAzl9hyOeNHQSpkigacISBxlZiyDHziYwWSl/8kdLhCS1p2/kOiwFtqFZQ BW6S/w5pIaFDcKM2XUTJYOcGzx3AnF+tBzjbsFVi4IMkXmJUAy4+7QuJ2gzIR8TWN4oM YF+DgK07vc15IuTGk8VfZv4ouHYKKkCd3v5Zm0aO0QOYGo88JC1sBjRAQsRH+sf8Dy4H jG9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=SuDvrAhwBFX92enbVknkRqvLgC7GvM+sj1KUtkTnyg4=; b=zIV3R9pO2zVjCu+Myhqw9z9jHc4JU7NTHpWW5QU7YOoT1k2tXDa7BiofT93qLEz/sm 3WZucIKSZ++H3eXx3xUYAujvgrAyaO9DRzbHhLcurRAIdgazjStHp8vMtezp94QH3MTU IWB5NUpm/F29L0hZ/iT8ifjZIKGv6GuDbZUSHoHEsp6zswonQPOGjysvZwj5+kP0di85 5+jbHR34BmRwZgOXN6CkfYv3QYOLrZZ1vpndRE6ZadAMo/mhdDeF3VayOSw62HjDhZZV i8zEuaFcWHEJ5DtdF++KKwnq+63nVcM0l7qwxR0lHIjiGIOO/mVlRFWbrHmcXpP1fm/Y jfEQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p26si1606499edx.191.2020.06.04.04.08.07; Thu, 04 Jun 2020 04:08:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726066AbgFDKd4 (ORCPT + 99 others); Thu, 4 Jun 2020 06:33:56 -0400 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:59193 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725601AbgFDKd4 (ORCPT ); Thu, 4 Jun 2020 06:33:56 -0400 X-IronPort-AV: E=Sophos;i="5.73,472,1583190000"; d="scan'208";a="452952018" Received: from abo-173-121-68.mrs.modulonet.fr (HELO hadrien) ([85.68.121.173]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2020 12:33:54 +0200 Date: Thu, 4 Jun 2020 12:33:53 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Joe Perches cc: Dan Carpenter , Linus Walleij , Christophe JAILLET , Robert Jarzmik , Daniel Mack , Haojian Zhuang , Linux ARM , "open list:GPIO SUBSYSTEM" , "linux-kernel@vger.kernel.org" , kernel-janitors@vger.kernel.org Subject: Re: [PATCH] pinctrl: pxa: pxa2xx: Remove 'pxa2xx_pinctrl_exit()' which is unused and broken In-Reply-To: <32232229031e02edcc268b1074c9bac44012ee35.camel@perches.com> Message-ID: References: <20200531073716.593343-1-christophe.jaillet@wanadoo.fr> <87h7vvb1s3.fsf@belgarion.home> <20200601183102.GS30374@kadam> <20200604083120.GF22511@kadam> <2aa49a543e6f48a6f428a37b63a06f9149870225.camel@perches.com> <32232229031e02edcc268b1074c9bac44012ee35.camel@perches.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 4 Jun 2020, Joe Perches wrote: > On Thu, 2020-06-04 at 11:52 +0200, Julia Lawall wrote: > > Should Fixes also be used when the change will make it hard to port other > > fixes over it? > > If it's a logic defect or regression that's being fixed, > shouldn't the logic defect or regression be fixed as > reasonably soon as possible? Sure, but I recall seeing some patches that mentioned that the problem had existed since the beginning of git. Of course, it should be rare. > > The nature of the fix should ideally be optimal for > backporting, but I believe that should not stop any > consideration for the standalone fix itself. I'm not sure to follow this. Sometimes non-bug fixes that block backporting a bug fix have to be backported as well. So the fixes would again highlight the range of versions affected by the issue. julia > What do you think? > >