From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Ingo Molnar <mingo@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
paulmck@linux.vnet.ibm.com,
Andrea Parri <andrea.parri@amarulasolutions.com>
Subject: [RFC PATCH v2 6/6] Documentation/features/vm: Remove arch support status file for 'pte_special'
Date: Sun, 8 Apr 2018 18:30:27 +0200 [thread overview]
Message-ID: <1523205027-31786-7-git-send-email-andrea.parri@amarulasolutions.com> (raw)
In-Reply-To: <1523205027-31786-1-git-send-email-andrea.parri@amarulasolutions.com>
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>
---
.../features/vm/pte_special/arch-support.txt | 33 ----------------------
1 file changed, 33 deletions(-)
delete mode 100644 Documentation/features/vm/pte_special/arch-support.txt
diff --git a/Documentation/features/vm/pte_special/arch-support.txt b/Documentation/features/vm/pte_special/arch-support.txt
deleted file mode 100644
index 6a608a6dcf71d..0000000000000
--- a/Documentation/features/vm/pte_special/arch-support.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-#
-# Feature name: pte_special
-# Kconfig: __HAVE_ARCH_PTE_SPECIAL
-# description: arch supports the pte_special()/pte_mkspecial() VM APIs
-#
- -----------------------
- | arch |status|
- -----------------------
- | alpha: | TODO |
- | arc: | ok |
- | arm: | ok |
- | arm64: | ok |
- | c6x: | TODO |
- | h8300: | TODO |
- | hexagon: | TODO |
- | ia64: | TODO |
- | m68k: | TODO |
- | microblaze: | TODO |
- | mips: | TODO |
- | nds32: | TODO |
- | nios2: | TODO |
- | openrisc: | TODO |
- | parisc: | TODO |
- | powerpc: | ok |
- | riscv: | TODO |
- | s390: | ok |
- | sh: | ok |
- | sparc: | ok |
- | um: | TODO |
- | unicore32: | TODO |
- | x86: | ok |
- | xtensa: | TODO |
- -----------------------
--
2.7.4
next prev parent reply other threads:[~2018-04-08 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 16:30 [RFC PATCH v2 0/6] Documentation/features: Provide and apply 'features-refresh.sh' Andrea Parri
2018-04-08 16:30 ` [RFC PATCH v2 1/6] Documentation/features: Add script that refreshes the arch support status files in place Andrea Parri
2018-04-08 16:30 ` [RFC PATCH v2 2/6] Documentation/features: Refresh " Andrea Parri
2018-04-08 16:30 ` [RFC PATCH v2 3/6] Documentation/features/core: Add arch support status files for 'cBPF-JIT' and 'eBPF-JIT' Andrea Parri
2018-04-08 16:30 ` [RFC PATCH v2 4/6] Documentation/features/locking: Use '!RWSEM_GENERIC_SPINLOCK' as Kconfig for 'rwsem-optimized' Andrea Parri
2018-04-08 16:30 ` [RFC PATCH v2 5/6] Documentation/features/lib: Remove arch support status file for 'strncasecmp' Andrea Parri
2018-04-08 16:30 ` Andrea Parri [this message]
2018-04-20 17:04 ` [RFC PATCH v2 0/6] Documentation/features: Provide and apply 'features-refresh.sh' Andrea Parri
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=1523205027-31786-7-git-send-email-andrea.parri@amarulasolutions.com \
--to=andrea.parri@amarulasolutions.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.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).