linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jason Wang <jasowang@redhat.com>, mst@redhat.com, jasowang@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	mikelley@microsoft.com, vkuznets@redhat.com, liuwe@microsoft.com,
	kkashanjat@microsoft.com, cohuck@redhat.com, otubo@redhat.com,
	andavis@redhat.com, aadam@redhat.com, stefanha@redhat.com,
	sgarzare@redhat.com, virtualization@lists.linux-foundation.org
Subject: Re: [RFC PATCH] virtio: document virtio hardening status and TODO
Date: Fri, 14 Oct 2022 08:01:58 -0600	[thread overview]
Message-ID: <87o7ueh5bd.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221014042037.23639-1-jasowang@redhat.com>

Jason Wang <jasowang@redhat.com> writes:

> This patch summarizes the status of hardening and TODO of hardening
> virtio core and drivers.
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
>  Documentation/security/virtio/core.rst | 49 ++++++++++++++++++++++++++
>  MAINTAINERS                            |  1 +
>  2 files changed, 50 insertions(+)
>  create mode 100644 Documentation/security/virtio/core.rst

Do you really need to create a new directory for a single file?

Regardless of where it sits, you'll need to add this file to an
index.rst file so that it becomes part of the docs build.

Thanks,

jon

  reply	other threads:[~2022-10-14 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  4:20 [RFC PATCH] virtio: document virtio hardening status and TODO Jason Wang
2022-10-14 14:01 ` Jonathan Corbet [this message]
2022-10-17  6:09   ` Jason Wang
2022-10-18 15:39 ` Stefano Garzarella

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=87o7ueh5bd.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=aadam@redhat.com \
    --cc=andavis@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kkashanjat@microsoft.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuwe@microsoft.com \
    --cc=mikelley@microsoft.com \
    --cc=mst@redhat.com \
    --cc=otubo@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vkuznets@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).