From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6062CC433E0 for ; Thu, 4 Jun 2020 11:08:41 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 34815207D5 for ; Thu, 4 Jun 2020 11:08:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ui9pgbWR" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 34815207D5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=perches.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=4rhrb1fI0TpX8VIZi3Fd8NfTEH1rHNKgQlj9ACyaLbQ=; b=ui9pgbWROAsZG7 KzGS+S8vGw9HQLHkDsl4kVl/Istqh9t1vJMhkLNTiWXy6TU88ILOEGSYk0Q4mfxcu3wH0MKyeR9BE N9ZyOeBEK4ddekDhHMwTALl27+Dt3Mz661qfdRJJIrp5wX/GOwBeB9Yb0x2UhGWDURAlcxqwWHI1m jqvvDEGsiWY3vGM4Z84T/fYs5QY0a4JsThey0gc5/ZBkfVxq8y3JlO8w/MR4ZvlKXn+/L25Ls1T9A t3IVZcWmsCuSkLO4KuLT7EZaOnUfxRaXwLkmKMxaDEaPfSu1pGm90wR7g0G9L+7+VSOtdH/N1CasC aUcSj0BP6iTuZtUzTCIQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jgnjk-0001Xf-Ro; Thu, 04 Jun 2020 11:08:40 +0000 Received: from smtprelay0197.hostedemail.com ([216.40.44.197] helo=smtprelay.hostedemail.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jgnji-0001XD-AT for linux-arm-kernel@lists.infradead.org; Thu, 04 Jun 2020 11:08:39 +0000 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay07.hostedemail.com (Postfix) with ESMTP id 0B734181D3030; Thu, 4 Jun 2020 11:08:36 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: sand99_0e162d926d96 X-Filterd-Recvd-Size: 3513 Received: from XPS-9350.home (unknown [47.151.136.130]) (Authenticated sender: joe@perches.com) by omf18.hostedemail.com (Postfix) with ESMTPA; Thu, 4 Jun 2020 11:08:34 +0000 (UTC) Message-ID: <10e54ee84bd44171ef329bed9e7e6a946bae61ba.camel@perches.com> Subject: Re: [PATCH] pinctrl: pxa: pxa2xx: Remove 'pxa2xx_pinctrl_exit()' which is unused and broken From: Joe Perches To: Julia Lawall Date: Thu, 04 Jun 2020 04:08:32 -0700 In-Reply-To: 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: Evolution 3.36.2-0ubuntu1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200604_040838_421691_F12048A7 X-CRM114-Status: GOOD ( 16.07 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux ARM , Linus Walleij , kernel-janitors@vger.kernel.org, "linux-kernel@vger.kernel.org" , Haojian Zhuang , "open list:GPIO SUBSYSTEM" , Christophe JAILLET , Dan Carpenter , Robert Jarzmik , Daniel Mack Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 2020-06-04 at 12:33 +0200, Julia Lawall wrote: > > 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. git history goes back 15 years already. There are scant few bugs that old. There is a tree with even older history that Rob Landley still has here: https://landley.net/kdocs/fullhist/ It does make git blame research a bit easier for those rare and extremely old defects. > > 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. I think it comes down to defects in current need to be fixed. Describing the base commit that is being fixed is useful for backporting. I believe it's not reasonable to ask the author of a fix to research how it could or should be backported. > 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. Sure, but the non-bug fixes that may also need backporting to enable easy backports of the actual fix should not be described in the Fixes: as those are generally easily researched from a command like: $ git log .. by whoever needs to backport. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel