workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	security@kernel.org, Kees Cook <keescook@chromium.org>,
	Sasha Levin <sashal@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
Date: Thu, 15 Feb 2024 13:24:57 +0100	[thread overview]
Message-ID: <26b25204-9829-44a8-9836-1ce1c8725586@oracle.com> (raw)
In-Reply-To: <2024021530-plank-cornmeal-90eb@gregkh>


On 15/02/2024 12:50, Greg Kroah-Hartman wrote:
> On Wed, Feb 14, 2024 at 09:37:31AM +0100, Vegard Nossum wrote:
>>
>> On 14/02/2024 09:00, Greg Kroah-Hartman wrote:
>>> diff --git a/Documentation/process/cve.rst b/Documentation/process/cve.rst
>>> new file mode 100644
>>> index 000000000000..6465e6a79c18
>>> --- /dev/null
>>> +++ b/Documentation/process/cve.rst
>>> @@ -0,0 +1,120 @@
>>> +CVEs
>>> +====
>>
>> Document titles should have ==== above them as well, and then you would
>> need to shift all the other headings in this document (i.e. all the ---
>> should become ===).
>>
>> Info here: https://docs.kernel.org/doc-guide/sphinx.html#specific-guidelines-for-the-kernel-documentation
> 
> Really?  I copied this directly from
> Documentation/process/security-bugs.rst which is in the format that I
> used here.  Which one is incorrect, I'm confused.

Documentation/ currently has a mix of both formats and they both work,
but the guidelines linked above is the gold standard and what we should
aim for in new documents.

The "correct" format would thus be:

====
CVEs
====

...

Process
=======

...

At least this is my understanding; I'm happy to be corrected (and in
this case, we should also update the documentation).

Thanks for your other clarifications.


Vegard

  reply	other threads:[~2024-02-15 12:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  8:00 Greg Kroah-Hartman
2024-02-14  8:34 ` Lukas Bulwahn
2024-02-15 12:04   ` Greg Kroah-Hartman
2024-02-15 16:10     ` Oleksandr Natalenko
2024-02-15 17:49       ` Greg Kroah-Hartman
2024-02-14  8:37 ` Vegard Nossum
2024-02-15 11:50   ` Greg Kroah-Hartman
2024-02-15 12:24     ` Vegard Nossum [this message]
2024-02-16  8:28       ` Jani Nikula
2024-02-16 11:22         ` Greg Kroah-Hartman
2024-02-16 14:58           ` Jonathan Corbet
2024-02-17 11:56             ` Greg Kroah-Hartman
2024-02-14 13:10 ` Krzysztof Kozlowski
2024-02-15 12:00   ` Greg Kroah-Hartman
2024-02-14 13:41 ` Konstantin Ryabitsev
2024-02-15 11:59   ` Greg Kroah-Hartman
2024-02-14 13:43 ` Jiri Kosina
2024-02-14 13:55   ` Mark Brown
2024-02-14 14:32     ` Greg Kroah-Hartman
2024-02-14 14:46     ` Jiri Kosina
2024-02-14 15:10       ` Mark Brown
2024-02-14 13:58   ` Greg Kroah-Hartman
2024-02-14 14:38     ` Jiri Kosina
2024-02-14 15:09       ` Greg Kroah-Hartman
2024-02-15  8:17 ` Thorsten Leemhuis
2024-02-15  8:43   ` Greg Kroah-Hartman
2024-02-15 17:54 ` Michal Hocko
2024-02-15 18:20   ` Greg Kroah-Hartman
2024-02-15 18:36     ` Michal Hocko
2024-02-16 11:25       ` Greg Kroah-Hartman
2024-02-16 13:20         ` Michal Hocko
2024-02-16 15:34           ` Greg Kroah-Hartman
2024-02-16 16:51             ` Michal Hocko
2024-02-15 19:40     ` Kees Cook
2024-02-16  7:41       ` Greg Kroah-Hartman

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=26b25204-9829-44a8-9836-1ce1c8725586@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=security@kernel.org \
    --cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox