From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Kosina <jikos@kernel.org>, Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Amit Shah <aams@amazon.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>,
Laura Abbott <labbott@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Solar Designer <solar@openwall.com>,
Thomas Gleixner <tglx@linutronix.de>,
Thorsten Leemhuis <linux@leemhuis.info>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Will Deacon <will@kernel.org>, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH v2] Documentation/security-bugs: overhaul
Date: Tue, 07 Jun 2022 07:30:10 -0600 [thread overview]
Message-ID: <87o7z4fvod.fsf@meer.lwn.net> (raw)
In-Reply-To: <nycvar.YFH.7.76.2206062326230.10851@cbobk.fhfr.pm>
Jiri Kosina <jikos@kernel.org> writes:
> - what sense does it make to have embargoed-hardware-issues.rst and
> security-bugs.rst live in different Documentation/ subdirectories
> (admin-guide/ vs process/)? It'd seem to make sense to me to have them
> in one common place?
Yes, I think that would make sense...a lot of stuff got sorted out into
the various guides quickly, and it didn't all land in the right place.
I'd be in favor of moving this over to the process guide, and perhaps
making a security-specific section there.
Thanks,
jon
next prev parent reply other threads:[~2022-06-07 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 19:48 [PATCH v2] Documentation/security-bugs: overhaul Vegard Nossum
2022-06-06 21:31 ` Jiri Kosina
2022-06-07 13:30 ` Jonathan Corbet [this message]
2022-06-07 14:00 ` Willy Tarreau
2022-06-07 9:07 ` Will Deacon
2022-06-07 13:06 ` Vegard Nossum
2022-06-09 14:51 ` Will Deacon
2022-06-09 17:01 ` Willy Tarreau
2023-03-05 14:38 ` Vegard Nossum
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=87o7z4fvod.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=aams@amazon.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=jikos@kernel.org \
--cc=keescook@chromium.org \
--cc=labbott@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mchehab@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=solar@openwall.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tyhicks@linux.microsoft.com \
--cc=vegard.nossum@oracle.com \
--cc=w@1wt.eu \
--cc=will@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