All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Nick Desaulniers" <ndesaulniers@google.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"# 3.4.x" <stable@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	"Jian Cai" <jiancai@google.com>, "Stefan Agner" <stefan@agner.ch>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	candle.sun@unisoc.com,
	"Miles Chen (陳民樺)" <miles.chen@mediatek.com>,
	"Stephen Hines" <srhines@google.com>,
	"Luis Lozano" <llozano@google.com>,
	"Sandeep Patil" <sspatil@google.com>,
	"Marc Zyngier" <maz@kernel.org>
Subject: Re: ARCH=arm LLVM_IAS=1 patches for 5.10, 5.4, and 4.19
Date: Mon, 15 Mar 2021 16:43:13 -0400	[thread overview]
Message-ID: <YE/G4ZGtFNDFw9ej@sashalap> (raw)
In-Reply-To: <YE+wNS1iiVTU8YGb@kroah.com>

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

      reply	other threads:[~2021-03-15 20:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 19:32 ARCH=arm LLVM_IAS=1 patches for 5.10, 5.4, and 4.19 Nick Desaulniers
2021-03-12 10:12 ` Greg KH
2021-03-12 17:28   ` Nick Desaulniers
2021-03-13  4:07     ` Sasha Levin
2021-03-15  9:08       ` Greg KH
2021-03-15  9:12         ` Greg KH
2021-03-15  9:16           ` Greg KH
2021-03-15 10:37             ` Ard Biesheuvel
2021-03-15 17:43               ` Nick Desaulniers
2021-03-15 17:53                 ` Ard Biesheuvel
2021-03-15 22:58                   ` Nick Desaulniers
2021-03-15 23:19                     ` [PATCH 5.4.y] ARM: 9030/1: entry: omit FP emulation for UND exceptions taken in kernel mode Nick Desaulniers
2021-03-16  6:20                       ` Ard Biesheuvel
2021-03-16 16:59                         ` [PATCH 5.4 2/2] ARM: 9044/1: vfp: use undef hook for VFP support detection Nick Desaulniers
2021-03-19 10:06                           ` Greg KH
2021-03-19 20:14                             ` Nick Desaulniers
2021-03-20 11:04                               ` Greg KH
2021-03-16 14:02                     ` ARCH=arm LLVM_IAS=1 patches for 5.10, 5.4, and 4.19 Sasha Levin
2021-03-15 19:06                 ` Greg KH
2021-03-15 20:43                   ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YE/G4ZGtFNDFw9ej@sashalap \
    --to=sashal@kernel.org \
    --cc=ardb@kernel.org \
    --cc=candle.sun@unisoc.com \
    --cc=catalin.marinas@arm.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiancai@google.com \
    --cc=llozano@google.com \
    --cc=maz@kernel.org \
    --cc=miles.chen@mediatek.com \
    --cc=ndesaulniers@google.com \
    --cc=samitolvanen@google.com \
    --cc=srhines@google.com \
    --cc=sspatil@google.com \
    --cc=stable@vger.kernel.org \
    --cc=stefan@agner.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.