workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, security@kernel.org,
	Sasha Levin <sashal@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] Documentation: Document the Linux Kernel CVE process
Date: Tue, 13 Feb 2024 12:20:30 -0700	[thread overview]
Message-ID: <87sf1w41dt.fsf@meer.lwn.net> (raw)
In-Reply-To: <2024021322-pumice-corny-eabc@gregkh>

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

> On Tue, Feb 13, 2024 at 07:48:12PM +0100, Greg Kroah-Hartman wrote:
>> The Linux kernel project now has the ability to assign CVEs to fixed
>> issues, so document the process and how individual developers can get a
>> CVE if one is not automatically assigned for their fixes.
>> 
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> Signed-off-by: Lee Jones <lee@kernel.org>
>> ---
>
> Jon, if you don't have any objections, I can just take this in my tree
> for the next -rc pull request I have for Linus with other driver-core
> type stuff.

Up to you - I probably have another 6.8 pull to do as well.  Happy
either way, if you want to push it:

Acked-by: Jonathan Corbet <corbet@lwn.net>

Thanks,

jon

  reply	other threads:[~2024-02-13 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 18:48 Greg Kroah-Hartman
2024-02-13 19:09 ` Greg Kroah-Hartman
2024-02-13 19:20   ` Jonathan Corbet [this message]
2024-02-13 19:56 ` Randy Dunlap
2024-02-14  7:15   ` Greg Kroah-Hartman
2024-02-14 16:44     ` Randy Dunlap
2024-02-13 22:35 ` Kees Cook
2024-02-14  6:43   ` Greg Kroah-Hartman
2024-02-14  7:45     ` Greg Kroah-Hartman
2024-02-14 19:02       ` Kees Cook

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=87sf1w41dt.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.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