From: Miaohe Lin <linmiaohe@huawei.com>
To: Michal Hocko <mhocko@suse.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 17:27:32 +0800 [thread overview]
Message-ID: <3a8857fd-d4f2-7743-d2e8-8580145d32e7@huawei.com> (raw)
In-Reply-To: <YUBJ3eA0a+Vk1wm4@dhcp22.suse.cz>
On 2021/9/14 15:06, Michal Hocko wrote:
> 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.
>
I see. Many thanks for your detailed explanation! :)
prev parent reply other threads:[~2021-09-14 9:28 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
2021-09-14 9:27 ` Miaohe Lin [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=3a8857fd-d4f2-7743-d2e8-8580145d32e7@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--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®