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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 6B1AAC4320A for ; Sun, 25 Jul 2021 23:45:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4BCAB60EB4 for ; Sun, 25 Jul 2021 23:45:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231192AbhGYXEz (ORCPT ); Sun, 25 Jul 2021 19:04:55 -0400 Received: from new3-smtp.messagingengine.com ([66.111.4.229]:37393 "EHLO new3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229829AbhGYXEx (ORCPT ); Sun, 25 Jul 2021 19:04:53 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 05C955807D5; Sun, 25 Jul 2021 19:45:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 25 Jul 2021 19:45:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=bUaoxm Us8Q89tzAaaWrITizZDB7ZNjUyiLAre6mVMUw=; b=o0pjfCN8VLX4lvyuYcHs6D hwUobXh5IJOMavo2dyrluS8rqrUqtmmI1GL+Q7pXjpTOpY1b0VJHYM3WeQreYxjn Bb6zD8mebvl4c0dk2oG6Ax6c5tNW9FqG9YI8dfj++aOFafhKSSqFluPvLYa8a6NH JNynO5r8t2iwVscPW5OCF5RCF9evJ3KGSBe1kZP2CAiDPcLs/ko+jZkJGi1kt7Ny jw/jZzflpg8g/BL69VMrydp1qH0eTsUJzwb519K56pvsJ2P2o9cIDkiVlZ5u/Cl+ 6WfEJgJQufnQ7NG0NjRKMIBh3/YbV2mXIG+tZtziC4dmXqu8mja3zcSK0qBOKIYw == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrgeeggddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcuvfhh rghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrghtth gvrhhnpeffudfhgeefvdeitedugfelueegheekkeefveffhfeiveetledvhfdtveffteeu udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehfth hhrghinheslhhinhhugidqmheikehkrdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 25 Jul 2021 19:45:18 -0400 (EDT) Date: Mon, 26 Jul 2021 09:44:27 +1000 (AEST) From: Finn Thain To: Geert Uytterhoeven cc: Greg Ungerer , Will Deacon , Peter Zijlstra , Boqun Feng , Brendan Jackman , kernel test robot , Arnd Bergmann , Alexander Viro , linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] m68k: Fix asm register constraints for atomic ops In-Reply-To: <20210725104618.365790-1-geert@linux-m68k.org> Message-ID: References: <20210725104618.365790-1-geert@linux-m68k.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 25 Jul 2021, Geert Uytterhoeven wrote: > Fixes: d839bae4269aea46 ("locking,arch,m68k: Fold atomic_ops") > ... > Technically, the issue was present before, but I doubt adding pre-v3.18 > Fixes tags would make any difference for stable... There is a better way to constrain backporting, that is Cc: stable@vger.kernel.org # 3.12+ The reason I mention it is that Fixes tags could be seen as a way to identify commits that introduce bugs, e.g. for the purposes of training AIs, or attributing blame, or measuring quality etc. I think it would be unfair to point the finger at Peter's commit.