linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kemeng Shi <shikemeng@huaweicloud.com>
To: pasha.tatashin@soleen.com, akpm@linux-foundation.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: shikemeng@huaweicloud.com
Subject: [PATCH 0/8] Remove unused parameters in page_table_check
Date: Fri, 14 Jul 2023 01:26:28 +0800	[thread overview]
Message-ID: <20230713172636.1705415-1-shikemeng@huaweicloud.com> (raw)

Hi all, this series remove unused parameters in functions from
page_table_check. The first 2 patches remove unused mm and addr
parameters in static common functions page_table_check_clear and
page_table_check_set. The last 6 patches remove unused addr parameter
in some externed functions which only need addr for cleaned
page_table_check_clear or page_table_check_set. There is no intended
functional change. Thanks!

Kemeng Shi (8):
  mm/page_table_check: remove unused parameters in
    page_table_check_clear()
  mm/page_table_check: remove unused parameters in
    page_table_check_set()
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pte_clear
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pmd_clear
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pud_clear
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pte_set
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pmd_set
  mm/page_table_check: remove unused parameter in
    [__]page_table_check_pud_set

 arch/arm64/include/asm/pgtable.h | 12 +++---
 arch/riscv/include/asm/pgtable.h | 12 +++---
 arch/x86/include/asm/pgtable.h   | 16 ++++----
 include/linux/page_table_check.h | 66 ++++++++++++--------------------
 include/linux/pgtable.h          |  6 +--
 mm/page_table_check.c            | 50 +++++++++---------------
 6 files changed, 65 insertions(+), 97 deletions(-)

-- 
2.30.0



             reply	other threads:[~2023-07-13  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 17:26 Kemeng Shi [this message]
2023-07-13 17:26 ` [PATCH 1/8] mm/page_table_check: remove unused parameters in page_table_check_clear() Kemeng Shi
2023-07-13 17:26 ` [PATCH 2/8] mm/page_table_check: remove unused parameters in page_table_check_set() Kemeng Shi
2023-07-13 17:26 ` [PATCH 3/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pte_clear Kemeng Shi
2023-07-13 17:26 ` [PATCH 4/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pmd_clear Kemeng Shi
2023-07-13 17:26 ` [PATCH 5/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pud_clear Kemeng Shi
2023-07-13 17:26 ` [PATCH 6/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pte_set Kemeng Shi
2023-07-13 17:26 ` [PATCH 7/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pmd_set Kemeng Shi
2023-07-13 17:26 ` [PATCH 8/8] mm/page_table_check: remove unused parameter in [__]page_table_check_pud_set Kemeng Shi
2023-07-22 21:48 ` [PATCH 0/8] Remove unused parameters in page_table_check Pasha Tatashin
2023-07-24 17:02   ` Andrew Morton
2023-07-24 17:17     ` Pasha Tatashin

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=20230713172636.1705415-1-shikemeng@huaweicloud.com \
    --to=shikemeng@huaweicloud.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox