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.
Unified · Split
| @@ -59,7 +59,7 @@ In addition, the following information are highly desirable: · 58 unmodified lines | ||
| 59 | 59 | immediately merged (see Documentation/process/submitting-patches.rst). |
| 60 | 60 | This will save some back-and-forth exchanges if it is accepted, and you |
| 61 | 61 | will be credited for finding and fixing this issue. Note that in this case |
| 62 | − only a ``Signed-off-by:`` tag is needed, without ``Reported-by:` when the | |
| 62 | + only a ``Signed-off-by:`` tag is needed, without ``Reported-by:`` when the | |
| 63 | 63 | reporter and author are the same. |
| 64 | 64 | |
| 65 | 65 | * **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 · 22 unmodified lines | ||
| 88 | 88 | are trusted, so the consequences of accidentally including the wrong maintainer |
| 89 | 89 | are essentially a bit more noise for that person, i.e. nothing dramatic. As |
| 90 | 90 | such, a suitable method to figure the list of maintainers (which kernel |
| 91 | −security officers use) is to rely on the get_maintainers.pl script, tuned to | |
| 91 | +security officers use) is to rely on the get_maintainer.pl script, tuned to | |
| 92 | 92 | only report maintainers. This script, when passed a file name, will look for |
| 93 | 93 | its path in the MAINTAINERS file to figure a hierarchical list of relevant |
| 94 | 94 | maintainers. Calling it a first time with the finest level of filtering will |