All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 12/12] docs: kernel-parameters.txt: remove reference for removed Intel MPX
Date: Tue, 17 Mar 2020 14:10:51 +0100	[thread overview]
Message-ID: <956bdad7bed30593175b7c1272e043f3804c5afb.1584450500.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1584450500.git.mchehab+huawei@kernel.org>

The Intel MPX support got removed on Kernel 5.6, but the
kernel-parameters file still mentions it.

Update the text to document that this parameter is not needed
anymore, as the Intel MPX will always be disabled now on
(as its support got removed).

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/admin-guide/kernel-parameters.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 192a36a66fc9..ff5e0ca7d9a7 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -990,9 +990,10 @@
 			Documentation/admin-guide/dynamic-debug-howto.rst
 			for details.
 
-	nompx		[X86] Disables Intel Memory Protection Extensions.
-			See Documentation/x86/intel_mpx.rst for more
-			information about the feature.
+	nompx		X86] Previously, disabled Intel Memory Protection
+			Extensions.
+			NOTE: It is now default, as the Intel MPX code
+			was removed in v5.6.
 
 	nopku		[X86] Disable Memory Protection Keys CPU feature found
 			in some Intel CPUs.
-- 
2.24.1


      parent reply	other threads:[~2020-03-17 13:11 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 13:10 [PATCH 00/12] Fix broken references for Documentation/* Mauro Carvalho Chehab
2020-03-17 13:10 ` Mauro Carvalho Chehab
2020-03-17 13:10 ` Mauro Carvalho Chehab
2020-03-17 13:10 ` Mauro Carvalho Chehab
2020-03-17 13:10 ` [Ocfs2-devel] " Mauro Carvalho Chehab
2020-03-17 13:10 ` [PATCH 01/12] MAINTAINERS: dt: update display/allwinner file entry Mauro Carvalho Chehab
2020-03-17 13:10 ` [PATCH 02/12] MAINTAINERS: dt: update etnaviv file reference Mauro Carvalho Chehab
2020-04-01 16:49   ` Rob Herring
2020-03-17 13:10 ` [PATCH 03/12] MAINTAINERS: drop an old reference to stm32 pwm timers doc Mauro Carvalho Chehab
2020-03-17 13:10 ` [PATCH 04/12] docs: dt: fix references to m_can.txt file Mauro Carvalho Chehab
     [not found]   ` <db67f9bc93f062179942f1e095a46b572a442b76.1584450500.git.mchehab+huawei-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2020-03-17 13:17     ` Marc Kleine-Budde
2020-03-17 13:17       ` Marc Kleine-Budde
2020-03-17 13:29       ` Dan Murphy
2020-03-17 13:29         ` Dan Murphy
     [not found]         ` <60f77c6f-0536-1f50-1b49-2f604026a5cb-l0cyMroinI0@public.gmane.org>
2020-03-17 13:54           ` Benjamin GAIGNARD
2020-03-17 13:54             ` Benjamin GAIGNARD
2020-03-17 14:06           ` Mauro Carvalho Chehab
2020-03-17 14:06             ` Mauro Carvalho Chehab
2020-03-30 21:05     ` Rob Herring
2020-03-30 21:05       ` Rob Herring
2020-03-17 13:10 ` [PATCH 05/12] docs: dt: fix references to ap806-system-controller.txt Mauro Carvalho Chehab
2020-03-17 13:50   ` Bartosz Golaszewski
2020-03-17 16:12   ` Miquel Raynal
2020-03-17 16:12     ` Miquel Raynal
2020-03-30 21:06   ` Rob Herring
2020-03-30 21:06     ` Rob Herring
2020-03-17 13:10 ` [PATCH 06/12] docs: dt: fix a broken reference to input.yaml Mauro Carvalho Chehab
2020-03-30 21:07   ` Rob Herring
2020-03-17 13:10 ` [PATCH 07/12] docs: dt: fix broken reference to phy-cadence-torrent.yaml Mauro Carvalho Chehab
2020-03-30 21:09   ` Rob Herring
2020-03-17 13:10 ` [PATCH 08/12] docs: fix broken references to text files Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:25   ` Jason Gunthorpe
2020-03-17 13:25     ` Jason Gunthorpe
2020-03-17 13:25     ` Jason Gunthorpe
2020-03-17 13:25     ` Jason Gunthorpe
2020-03-17 13:25     ` Jason Gunthorpe
2020-03-17 14:36   ` Mathieu Poirier
2020-03-17 14:36     ` Mathieu Poirier
2020-03-17 14:36     ` Mathieu Poirier
2020-03-17 14:36     ` Mathieu Poirier
2020-03-17 13:10 ` [PATCH 09/12] docs: fix broken references for ReST files that moved around Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-31  9:09   ` Corentin Labbe
2020-03-31  9:09     ` Corentin Labbe
2020-03-17 13:10 ` [PATCH 10/12] docs: dt: display/ti: fix typos at the devicetree/ directory name Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:37   ` Jyri Sarha
2020-03-17 13:37     ` Jyri Sarha
2020-03-30 21:15   ` Rob Herring
2020-03-30 21:15     ` Rob Herring
2020-03-17 13:10 ` [PATCH 11/12] docs: filesystems: fix renamed references Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` Mauro Carvalho Chehab
2020-03-17 13:10   ` [Ocfs2-devel] " Mauro Carvalho Chehab
2020-03-17 13:10 ` Mauro Carvalho Chehab [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=956bdad7bed30593175b7c1272e043f3804c5afb.1584450500.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.