From: Andrew Morton <akpm@linux-foundation.org>
To: Marco Elver <elver@google.com>
Cc: Peter Collingbourne <pcc@google.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] kasan: update function name in comments
Date: Wed, 23 Feb 2022 20:07:47 -0800 [thread overview]
Message-ID: <20220223200747.2487235367d74255d8e13ba9@linux-foundation.org> (raw)
In-Reply-To: <CANpmjNMyuQh-G0kLOdoFWXyhw31PJsjXgbv7Qy+774v8iq9NWw@mail.gmail.com>
On Thu, 24 Feb 2022 00:35:32 +0100 Marco Elver <elver@google.com> wrote:
> > I thought that Cc: stable@vger.kernel.org controlled whether the patch
> > is to be taken to the stable kernel and Fixes: was more of an
> > informational tag. At least that's what this seems to say:
> > https://www.kernel.org/doc/html/latest/process/submitting-patches.html#reviewer-s-statement-of-oversight
>
> These days patches that just have a Fixes tag (and no Cc: stable) will
> be auto-picked in many (most?) cases (by empirical observation).
>
> I think there were also tree-specific variances of this policy, but am
> not sure anymore. What is the latest policy?
The -stable maintainers have been asked not to do that for MM patches -
to only take those which the developers (usually I) have explicitly tagged
for backporting.
I don't know how rigorously this is being followed. Probably OK for
patches to mm/* but if it's drivers/base/node.c then heaven knows.
next prev parent reply other threads:[~2022-02-24 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 1:24 Peter Collingbourne
2022-02-19 2:00 ` Miaohe Lin
2022-02-21 11:15 ` Marco Elver
2022-02-23 22:30 ` Peter Collingbourne
2022-02-23 23:35 ` Marco Elver
2022-02-24 4:07 ` Andrew Morton [this message]
2022-02-22 16:38 ` Andrey Konovalov
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=20220223200747.2487235367d74255d8e13ba9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=sashal@kernel.org \
/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