public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
* Documentation: fix two typos in latest update to the security report howto
@ 2026-04-04  8:20 Willy Tarreau
  0 siblings, 0 replies; only message in thread
From: Willy Tarreau @ 2026-04-04  8:20 UTC (permalink / raw)
  To: greg
  Cc: Jonathan Corbet, skhan, workflows, linux-doc, linux-kernel,
	Willy Tarreau

In previous patch "Documentation: clarify the mandatory and desirable
info for security reports" I left two typos that I didn't detect in local
checks. One is "get_maintainers.pl" (no 's' in the script name), and the
other one is a missing closing quote after "Reported-by", which didn't
have effect here but I don't know if it can break rendering elsewhere
(e.g. on the public HTML page). Better fix it before it gets merged.

Signed-off-by: Willy Tarreau <w@1wt.eu>
---

Greg, this is a fix for commit a72b832a482372 that is currently pending
in your char-misc-linus branch.
---
 Documentation/process/security-bugs.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/process/security-bugs.rst b/Documentation/process/security-bugs.rst
index 0b1f6d8e3cbe..27b028e85861 100644
--- a/Documentation/process/security-bugs.rst
+++ b/Documentation/process/security-bugs.rst
@@ -59,7 +59,7 @@ In addition, the following information are highly desirable:
     immediately merged (see Documentation/process/submitting-patches.rst).
     This will save some back-and-forth exchanges if it is accepted, and you
     will be credited for finding and fixing this issue.  Note that in this case
-    only a ``Signed-off-by:`` tag is needed, without ``Reported-by:` when the
+    only a ``Signed-off-by:`` tag is needed, without ``Reported-by:`` when the
     reporter and author are the same.
 
   * **mitigations**: very often during a bug analysis, some ways of mitigating
@@ -88,7 +88,7 @@ recipients to send a report to.  In the Linux kernel, all official maintainers
 are trusted, so the consequences of accidentally including the wrong maintainer
 are essentially a bit more noise for that person, i.e. nothing dramatic.  As
 such, a suitable method to figure the list of maintainers (which kernel
-security officers use) is to rely on the get_maintainers.pl script, tuned to
+security officers use) is to rely on the get_maintainer.pl script, tuned to
 only report maintainers.  This script, when passed a file name, will look for
 its path in the MAINTAINERS file to figure a hierarchical list of relevant
 maintainers.  Calling it a first time with the finest level of filtering will
-- 
2.52.0


^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2026-04-04  8:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-04  8:20 Documentation: fix two typos in latest update to the security report howto Willy Tarreau

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox