From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <naoya.horiguchi@nec.com>, <willy@infradead.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] A few fixup patches for mm
Date: Fri, 28 Jul 2023 10:20:25 +0800 [thread overview]
Message-ID: <b0d91f3f-764d-59d1-98c1-95fa6788cb2a@huawei.com> (raw)
In-Reply-To: <20230727095701.98b4dba128292d0128f44858@linux-foundation.org>
On 2023/7/28 0:57, Andrew Morton wrote:
> On Thu, 27 Jul 2023 19:56:39 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
>
>> This series contains a few fixup patches to fix potential unexpected
>> return value, fix wrong swap entry type for hwpoisoned swapcache page
>> and so on. More details can be found in the respective changelogs.
>
> I'm thinking that patches 1-3 should be backported into -stable kernels.
> Thoughts on this?
I tend to backport the patches 1-3. They helps.
Thanks Andrew.
prev parent reply other threads:[~2023-07-28 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:56 Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 1/4] mm/swapfile: fix wrong swap entry type for hwpoisoned swapcache page Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 2/4] mm: memory-failure: fix potential unexpected return value from unpoison_memory() Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 3/4] mm: memory-failure: avoid false hwpoison page mapped error info Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 4/4] mm: memory-failure: add PageOffline() check Miaohe Lin
2023-07-27 16:57 ` [PATCH v2 0/4] A few fixup patches for mm Andrew Morton
2023-07-28 2:20 ` 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=b0d91f3f-764d-59d1-98c1-95fa6788cb2a@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=willy@infradead.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