linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kemeng Shi <shikemeng@huaweicloud.com>
To: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] minor cleanups to page_ext header
Date: Wed, 19 Jul 2023 11:41:09 +0800	[thread overview]
Message-ID: <fd753649-537f-af47-6ab5-1eea351c1c84@huaweicloud.com> (raw)
In-Reply-To: <20230717113227.1897173-1-shikemeng@huaweicloud.com>

Hi Andrew, sorry for the bother. I notice that you have taken my patches sent
later and I do appreciate it. I send this email just to avoid this series sent
early is missed for some unknow reasons. Thanks!

on 7/17/2023 7:32 PM, Kemeng Shi wrote:
> Hi all, this series does page_ext header relevant cleanups.
> First two patches remove unused page_ext header from page_poison and
> vmstat. The last patch move page_ext_operations definition under
> CONFIG_PAGE_EXTENSION. Thanks!
> 
> Kemeng Shi (3):
>   mm/page_poison: remove unused page_ext.h from page_poison
>   mm/vmstat: remove unused page_ext.h from vmstat
>   mm/page_ext: move page_ext_operations definition under
>     CONFIG_PAGE_EXTENSION
> 
>  include/linux/page_ext.h | 3 +--
>  mm/page_poison.c         | 1 -
>  mm/vmstat.c              | 1 -
>  3 files changed, 1 insertion(+), 4 deletions(-)
> 

-- 
Best wishes
Kemeng Shi



      parent reply	other threads:[~2023-07-19  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230717113227.1897173-1-shikemeng@huaweicloud.com>
2023-07-17 11:32 ` [PATCH 1/3] mm/page_poison: remove unused page_ext.h from page_poison Kemeng Shi
2023-07-17 11:32 ` [PATCH 2/3] mm/vmstat: remove unused page_ext.h from vmstat Kemeng Shi
2023-07-17 11:32 ` [PATCH 3/3] mm/page_ext: move page_ext_operations definition under CONFIG_PAGE_EXTENSION Kemeng Shi
2023-07-19  3:41 ` Kemeng Shi [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=fd753649-537f-af47-6ab5-1eea351c1c84@huaweicloud.com \
    --to=shikemeng@huaweicloud.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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