summaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorWilly Tarreau <w@1wt.eu>2025-08-14 21:27:30 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-08-17 12:23:30 +0200
commit3a68841d1d9b6eb32b2652bbb83acd17d5eb9135 (patch)
treecedbd96d90dd7ca262fdea7dad14979598a1ac7e /tools/perf/util/scripting-engines/trace-event-python.c
parentd49172bbd7eb07e4ba5e52238eaa9caf692c1cea (diff)
Documentation: smooth the text flow in the security bug reporting process
The text was presenting the team, the the e-mail address, then some of the expectations, then what form of e-mail is expected. By switching the e-mail paragraph two paragraphs later and dropping the "Contact" sub-section, we can have a more natural flow that presents the team, then its expectation, then how to best contribute, then where to send. And more importantly, it increases the chances that reporters have read the prerequisites before finding the e-mail address. Signed-off-by: Willy Tarreau <w@1wt.eu> Reviewed-by: Kees Cook <kees@kernel.org> Link: https://lore.kernel.org/r/20250814192730.19252-2-w@1wt.eu Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions