From: Michal Hocko <mhocko@suse.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/page_isolation: fix potential missing call to unset_migratetype_isolate()
Date: Tue, 14 Sep 2021 09:06:05 +0200 [thread overview]
Message-ID: <YUBJ3eA0a+Vk1wm4@dhcp22.suse.cz> (raw)
In-Reply-To: <1d0e15ab-4a1f-0820-26c2-4b9949164dfa@huawei.com>
On Tue 14-09-21 11:09:47, Miaohe Lin wrote:
[...]
> So even the Fixes tag should be removed ?
I would keep that one there. Fixes tag is useful to frame the scope of
the fix. For example when somebody is backporting the commit mentioned
in the Fixes tag then a) a lot of follow up patches with Fixes can tell
you this won't be an easy ride and you might want to reconsider risks
vs. benefit b) it helps to collect follow up fixes more easily.
That is a different story from cc: stable which just collects patches
and push them to all consumers of the stable branch if they apply.
To conclude, the Fixes tag is a generaly useful tag to bind patches
together and let people evaluate how important that is while Cc stable
is an indication that a fix is serious enough to push to all stable
users.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-09-14 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 11:51 Miaohe Lin
2021-09-13 12:12 ` Michal Hocko
2021-09-13 12:20 ` David Hildenbrand
2021-09-13 12:43 ` Miaohe Lin
2021-09-13 12:59 ` Michal Hocko
2021-09-14 2:51 ` Andrew Morton
2021-09-14 3:10 ` Miaohe Lin
2021-09-14 3:09 ` Miaohe Lin
2021-09-14 7:06 ` Michal Hocko [this message]
2021-09-14 9:27 ` Miaohe Lin
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=YUBJ3eA0a+Vk1wm4@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®