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=-6.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 C8332C433DB for ; Mon, 15 Mar 2021 20:44:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9C2AE64F26 for ; Mon, 15 Mar 2021 20:44:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231559AbhCOUnl (ORCPT ); Mon, 15 Mar 2021 16:43:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:50390 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232741AbhCOUnO (ORCPT ); Mon, 15 Mar 2021 16:43:14 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0806F64F01; Mon, 15 Mar 2021 20:43:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615840994; bh=IVYQn8WxFP9IQ+eQj6c/g9F2LLfY7Y7JElDpXVrfo6g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MWDW3XIO9iLgI2lQzQe6gUHMIQmsWnYGiYRE8YogxZ6HphEjBn51WkN+JSDW85VNQ nTv4cjwt8/Hib7mqSajoAeJrvSZIpolXaz1wWqKkaRcYmr0Zpn7uLHuMTce+Qiyn9z ysUE9VLNbjM7edUm12/QAfrqB62h82EiWRu2gAfQ0HlGZLLGZvnWwJ0h0/L6BurXqs sPeDGrYOZ8+RGMZItfVrWEd0b2+yOp6wLBb4ASWTC6eU/9dlg+JyPpej263DhnCyoq zWU11jolHfq7Vyzk+MjXYgKJHeu+j5VOdIR3Ue1f4gGPkbJCAgOQ1eJDwlKkCuyD41 iLr/EJRb4N0Mg== Date: Mon, 15 Mar 2021 16:43:13 -0400 From: Sasha Levin To: Greg KH Cc: Nick Desaulniers , Ard Biesheuvel , "# 3.4.x" , clang-built-linux , Jian Cai , Stefan Agner , Catalin Marinas , Sami Tolvanen , candle.sun@unisoc.com, Miles Chen =?utf-8?B?KOmZs+awkeaouik=?= , Stephen Hines , Luis Lozano , Sandeep Patil , Marc Zyngier Subject: Re: ARCH=arm LLVM_IAS=1 patches for 5.10, 5.4, and 4.19 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Mar 15, 2021 at 08:06:29PM +0100, Greg KH wrote: >On Mon, Mar 15, 2021 at 10:43:26AM -0700, Nick Desaulniers wrote: >> Then it should be possible for any patch >> that itself is backported (contains "commit XXX upstream") to be fed >> in when auto selected or submitted to stable (or before then) to check >> for new fixes. Probably would still need to be run periodically, as >> Fixes: aren't necessarily available when AutoSel runs. For the >> toolchain, we have a bot that watches for reverts for example, but >> non-standard commit messages denoting one patch fixes another makes >> this far from perfect. Would still need to be run periodically, >> because if a Fixes: exists, but hasn't been merged yet, it could get >> missed. > >I do re-run my script at times, it does require it to be run every once >in a while. But again, who is going to care about this except me and >Sasha? I actually run something like that often, there are tons of patches with Fixes: that points to commits in the stable tree, but quite a few need a less-than-trivial backport that no one did. >> Though I'm curious how the machinery that picks up Fixes: tags works. >> Does it run on a time based cadence? Is it only run as part of >> AutoSel, but not for manual backports sent to the list? Would it have >> picked up on f77ac2e378be at some point? > >Maybe it will, mine might have picked it up, who knows, I haven't run it >in a while. But as you say, because it fails to apply, that's a good >reason for me to not backport it. I run it on a weekly basis for *new* commits. -- Thanks, Sasha