public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Security Officers <security@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Add the security document to SECURITY CONTACT
Date: Fri, 28 Aug 2020 10:07:53 +0200	[thread overview]
Message-ID: <20200828080753.GA1007318@kroah.com> (raw)
In-Reply-To: <20200827182029.3458-1-krzk@kernel.org>

On Thu, Aug 27, 2020 at 08:20:29PM +0200, Krzysztof Kozlowski wrote:
> When changing the document related to kernel security workflow, notify
> the security mailing list as its concerned by this.
> 
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: <security@kernel.org>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> 
> ---
> 
> Changes since v1:
> 1. Changed order - F: go to end of entry,
> 2. Remove embargoed-hardware-issues
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8107b3d5d6df..19064a4ae9b0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15621,6 +15621,7 @@ F:	include/uapi/linux/sed*
>  SECURITY CONTACT
>  M:	Security Officers <security@kernel.org>
>  S:	Supported
> +F:	Documentation/admin-guide/security-bugs.rst
>  
>  SECURITY SUBSYSTEM
>  M:	James Morris <jmorris@namei.org>
> -- 
> 2.17.1
> 

Thanks, I'll queue this up in my tree...

greg k-h

      reply	other threads:[~2020-08-28  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 18:20 [PATCH v2] MAINTAINERS: Add the security document to SECURITY CONTACT Krzysztof Kozlowski
2020-08-28  8:07 ` Greg Kroah-Hartman [this message]

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=20200828080753.GA1007318@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@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