linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siddhant Gupta <siddhantgupta416@gmail.com>
To: corbet@lwn.net
Cc: mortonm@chromium.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, mamtashukla555@gmail.com,
	himadrispandya@gmail.com
Subject: [PATCH] Documentation: admin-guide: LSM: improve the title underline
Date: Thu, 12 Nov 2020 14:43:53 +0530	[thread overview]
Message-ID: <20201112091353.GA19262@Sleakybeast> (raw)

Fix warning of title underline too short

Signed-off-by: Siddhant Gupta <siddhantgupta416@gmail.com>
---
 Documentation/admin-guide/LSM/SafeSetID.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/LSM/SafeSetID.rst b/Documentation/admin-guide/LSM/SafeSetID.rst
index 17996c9070e2..0ec34863c674 100644
--- a/Documentation/admin-guide/LSM/SafeSetID.rst
+++ b/Documentation/admin-guide/LSM/SafeSetID.rst
@@ -107,7 +107,7 @@ for a UID/GID will prevent that UID/GID from obtaining auxiliary setid
 privileges, such as allowing a user to set up user namespace UID/GID mappings.
 
 Note on GID policies and setgroups()
-==================
+====================================
 In v5.9 we are adding support for limiting CAP_SETGID privileges as was done
 previously for CAP_SETUID. However, for compatibility with common sandboxing
 related code conventions in userspace, we currently allow arbitrary
-- 
2.25.1


             reply	other threads:[~2020-11-12  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  9:13 Siddhant Gupta [this message]
2020-11-13 22:00 ` [PATCH] Documentation: admin-guide: LSM: improve the title underline Jonathan Corbet

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=20201112091353.GA19262@Sleakybeast \
    --to=siddhantgupta416@gmail.com \
    --cc=corbet@lwn.net \
    --cc=himadrispandya@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mamtashukla555@gmail.com \
    --cc=mortonm@chromium.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;
as well as URLs for NNTP newsgroup(s).