All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	Naoya Horiguchi <naoya.horiguchi@nec.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] mm: memory-failure: make action_result() return int
Date: Tue, 25 Oct 2022 11:07:48 +0800	[thread overview]
Message-ID: <2045a25b-368b-1590-a787-fc802a7a8eb4@huawei.com> (raw)
In-Reply-To: <20221024035138.99119-1-wangkefeng.wang@huawei.com>

On 2022/10/24 11:51, Kefeng Wang wrote:
> Check mf_result in action_result(), only return 0 when
> MF_RECOVERED/MF_DELAYED, or return -EBUSY, which will
> simplify code a bit.
> 
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>

Thanks for cleanup. This really makes code cleaner.

Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>

Thanks,
Miaohe Lin



  parent reply	other threads:[~2022-10-25  3:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:46 [PATCH 1/3] mm: memory-failure: make put_ref_page() more useful Kefeng Wang
2022-10-21  8:46 ` [PATCH 2/3] mm: memory-failure: avoid pfn_valid() twice in soft_offline_page() Kefeng Wang
2022-10-23 23:39   ` HORIGUCHI NAOYA(堀口　直也)
2022-10-25  2:55   ` Miaohe Lin
2022-10-21  8:46 ` [PATCH 3/3] mm: memory-failure: make action_result() return int Kefeng Wang
2022-10-23 23:56   ` HORIGUCHI NAOYA(堀口　直也)
2022-10-24  1:39     ` Kefeng Wang
2022-10-24  3:51   ` [PATCH v2] " Kefeng Wang
2022-10-24  7:35     ` HORIGUCHI NAOYA(堀口　直也)
2022-10-25  3:07     ` Miaohe Lin [this message]
2022-10-23 23:38 ` [PATCH 1/3] mm: memory-failure: make put_ref_page() more useful HORIGUCHI NAOYA(堀口　直也)
2022-10-25  2:52 ` 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=2045a25b-368b-1590-a787-fc802a7a8eb4@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=wangkefeng.wang@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.