workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	security@kernel.org, corbet@lwn.net, workflows@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kees Cook <keescook@chromium.org>,
	Solar Designer <solar@openwall.com>,
	Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [RFC PATCH] Documentation: security-bugs.rst: linux-distros relaxed their rules
Date: Thu, 12 Oct 2023 18:06:43 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2310121805480.3534@cbobk.fhfr.pm> (raw)
In-Reply-To: <20231007140454.25419-1-w@1wt.eu>

On Sat, 7 Oct 2023, Willy Tarreau wrote:

> The linux-distros list relaxed their rules to try to adapt better to
> how the Linux kernel works. Let's update the Coordination part to
> explain why and when to contact them or not to and how to avoid trouble
> in the future.
> 
> Link: https://www.openwall.com/lists/oss-security/2023/09/08/4
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Solar Designer <solar@openwall.com>
> Cc: Vegard Nossum <vegard.nossum@oracle.com>
> Signed-off-by: Willy Tarreau <w@1wt.eu>

With my distro hat on:

	Acked-by: Jiri Kosina <jkosina@suse.cz>

Thanks a lot,

-- 
Jiri Kosina
SUSE Labs


      parent reply	other threads:[~2023-10-12 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 14:04 Willy Tarreau
2023-10-07 16:30 ` Vegard Nossum
2023-10-07 16:39   ` Willy Tarreau
2023-10-12 21:51     ` Solar Designer
2023-10-13  3:47       ` Willy Tarreau
2023-10-13  6:54         ` Jiri Kosina
2023-10-13  7:08           ` Willy Tarreau
2023-10-12 16:06 ` Jiri Kosina [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=nycvar.YFH.7.76.2310121805480.3534@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=solar@openwall.com \
    --cc=vegard.nossum@oracle.com \
    --cc=w@1wt.eu \
    --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