linux-kernel - Re: linux-next: Fixes tags need some work in the pinctrl tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkday2DXDNJJJ7srC5-Fj_d9iiqX-nqY9np1TnsBsOG6sCg@mail.gmail.com>
Date:   Mon, 25 Apr 2022 15:33:06 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Caleb Connolly <kc@...tmarketos.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the pinctrl tree

On Mon, Apr 25, 2022 at 2:27 PM Caleb Connolly <kc@...tmarketos.org> wrote:

> The patch shouldn't be backported to stable as it will introduce a bug if ported
> without the second patch (and as above, I don't think this series should be
> backported at all). Could you let me know how to get this dropped from backporting?

If Greg or Sasha etc propose the patch for stable (which will not happen
automatically unless you explicitly add Cc: stable@...r.kernel.org)
they send out a proposal "I will add this patch to stable", with CC to the
author, and then you can say you don't want it backported.

Many Fixes:-tagged patches do not get picked up for stable, it is not
what the tag means, if you want things to be picked for stable, the
rule is Cc: stable@, it's just that sometimes the stable maintainers
(and an AI!) pick some Fixes: patches anyways.

Yours,
Linus Walleij