From: Caleb Connolly <kc@postmarketos.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the pinctrl tree
Date: Mon, 25 Apr 2022 14:35:24 +0100 [thread overview]
Message-ID: <dbc168d8-5f37-7f75-16d0-18f3b8df4bd9@postmarketos.org> (raw)
In-Reply-To: <CACRpkday2DXDNJJJ7srC5-Fj_d9iiqX-nqY9np1TnsBsOG6sCg@mail.gmail.com>
On 25/04/2022 14:33, Linus Walleij wrote:
> On Mon, Apr 25, 2022 at 2:27 PM Caleb Connolly <kc@postmarketos.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@vger.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.
Ah ok, that's a relief. Thanks for the explanation!
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2022-04-25 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 23:10 linux-next: Fixes tags need some work in the pinctrl tree Stephen Rothwell
2022-04-21 22:31 ` Stephen Rothwell
2022-04-22 20:57 ` Linus Walleij
2022-04-25 12:27 ` Caleb Connolly
2022-04-25 13:33 ` Linus Walleij
2022-04-25 13:35 ` Caleb Connolly [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=dbc168d8-5f37-7f75-16d0-18f3b8df4bd9@postmarketos.org \
--to=kc@postmarketos.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).