From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, rick.p.edgecombe@intel.com,
corbet@lwn.net, akpm@linux-foundation.org,
anshuman.khandual@arm.com, akpm@linux-foundation.org
Subject: + documentation-mm-drop-pte_bad-descriptions-from-arch-page-table-helpers.patch added to mm-unstable branch
Date: Tue, 14 Nov 2023 15:26:05 -0800 [thread overview]
Message-ID: <20231114232606.69C0FC433C8@smtp.kernel.org> (raw)
The patch titled
Subject: Documentation/mm: drop pte_bad() descriptions from arch page table helpers
has been added to the -mm mm-unstable branch. Its filename is
documentation-mm-drop-pte_bad-descriptions-from-arch-page-table-helpers.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/documentation-mm-drop-pte_bad-descriptions-from-arch-page-table-helpers.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Documentation/mm: drop pte_bad() descriptions from arch page table helpers
Date: Tue, 14 Nov 2023 12:04:56 +0530
pte_bad() never existed unlike similar helpers at PMU, PUD, and PGD level.
This was added erroneously and hence should be dropped instead.
Link: https://lkml.kernel.org/r/20231114063456.339652-1-anshuman.khandual@arm.com
Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/mm/arch_pgtable_helpers.rst | 2 --
1 file changed, 2 deletions(-)
--- a/Documentation/mm/arch_pgtable_helpers.rst~documentation-mm-drop-pte_bad-descriptions-from-arch-page-table-helpers
+++ a/Documentation/mm/arch_pgtable_helpers.rst
@@ -18,8 +18,6 @@ PTE Page Table Helpers
+---------------------------+--------------------------------------------------+
| pte_same | Tests whether both PTE entries are the same |
+---------------------------+--------------------------------------------------+
-| pte_bad | Tests a non-table mapped PTE |
-+---------------------------+--------------------------------------------------+
| pte_present | Tests a valid mapped PTE |
+---------------------------+--------------------------------------------------+
| pte_young | Tests a young PTE |
_
Patches currently in -mm which might be from anshuman.khandual@arm.com are
documentation-mm-drop-pte_bad-descriptions-from-arch-page-table-helpers.patch
reply other threads:[~2023-11-14 23:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231114232606.69C0FC433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rick.p.edgecombe@intel.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;
as well as URLs for NNTP newsgroup(s).