From: Willy Tarreau <w@1wt.eu>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: threat-model: add missing closing parenthesis
Date: Sun, 17 May 2026 18:04:04 +0200 [thread overview]
Message-ID: <agnm9A9SFsmvIFZg@1wt.eu> (raw)
In-Reply-To: <da8ee1e8b4e99261ec11544c4e1a4f81316ae965.1779032501.git.baruch@tkos.co.il>
On Sun, May 17, 2026 at 06:41:41PM +0300, Baruch Siach wrote:
> Fixes: a03ef333fbd6 ("Documentation: security-bugs: explain what is and is not a security bug")
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Thank you, and sorry for this mistake!
Obviously: Acked-by: Willy Tarreau <w@1wt.eu>
Willy
> ---
> Documentation/process/threat-model.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/threat-model.rst b/Documentation/process/threat-model.rst
> index f177b8d3c1ca..9dd8011dde82 100644
> --- a/Documentation/process/threat-model.rst
> +++ b/Documentation/process/threat-model.rst
> @@ -176,7 +176,7 @@ regular bug:
> * problems seen only under development simulators, emulators, or combinations
> that do not exist on real systems at the time of reporting (issues
> involving tens of millions of threads, tens of thousands of CPUs,
> - unrealistic CPU frequencies, RAM sizes or disk capacities, network speeds.
> + unrealistic CPU frequencies, RAM sizes or disk capacities, network speeds).
>
> * issues whose reproduction requires hardware modification or emulation,
> including fake USB devices that pretend to be another one.
> --
> 2.53.0
next prev parent reply other threads:[~2026-05-17 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 15:41 [PATCH] docs: threat-model: add missing closing parenthesis Baruch Siach
2026-05-17 16:04 ` Willy Tarreau [this message]
2026-05-25 20:19 ` Jonathan Corbet
2026-05-25 20:26 ` Willy Tarreau
2026-05-25 21:33 ` Konstantin Ryabitsev
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=agnm9A9SFsmvIFZg@1wt.eu \
--to=w@1wt.eu \
--cc=baruch@tkos.co.il \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.