mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, mingo@kernel.org,
	byungchul.park@lge.com, David Sterba <dsterba@suse.com>
Subject: [PATCH] Documentation: remove stale crossrelease_stacktrace parameter
Date: Mon,  8 Jan 2018 16:27:31 +0100	[thread overview]
Message-ID: <20180108152731.27613-1-dsterba@suse.com> (raw)

The cross-release lockdep functionality has been removed in
e966eaeeb623f0997 ("locking/lockdep: Remove the cross-release locking
checks"), leaving the kernel parameter docs behind. The code handling
the parameter does not exist so this is a plain documentation change.

Signed-off-by: David Sterba <dsterba@suse.com>
---
 Documentation/admin-guide/kernel-parameters.txt | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index af7104aaffd9..a626465dd877 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -713,9 +713,6 @@
 			It will be ignored when crashkernel=X,high is not used
 			or memory reserved is below 4G.
 
-	crossrelease_fullstack
-			[KNL] Allow to record full stack trace in cross-release
-
 	cryptomgr.notests
                         [KNL] Disable crypto self-tests
 
-- 
2.15.1

             reply	other threads:[~2018-01-08 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 15:27 David Sterba [this message]
2018-01-08 17:25 ` [tip:locking/urgent] locking/Documentation: Remove stale crossrelease_fullstack parameter tip-bot for David Sterba

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=20180108152731.27613-1-dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=byungchul.park@lge.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome