qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH] Documentation: create/move s390x documentation
Date: Wed, 18 Mar 2020 15:40:32 +0100	[thread overview]
Message-ID: <20200318154032.6636c449.cohuck@redhat.com> (raw)
In-Reply-To: <20200318103940.1169-1-cohuck@redhat.com>

On Wed, 18 Mar 2020 11:39:40 +0100
Cornelia Huck <cohuck@redhat.com> wrote:

> Create a subdirectory for s390x under docs/system/ and move the
> existing vfio-ap documentation there.
> 
> Create an initial document describing s390x system emulation.
> 
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> 
> Mostly an initial version so that Janosch can base his protected virt
> documentation on something; there's room for more here :)
> 
> If this looks good, I'll queue it on my s390-next branch for 5.1.
> 
> ---
>  MAINTAINERS                         |  5 +++--
>  docs/system/index.rst               |  1 -
>  docs/system/{ => s390x}/vfio-ap.rst |  0
>  docs/system/target-s390x.rst        | 26 ++++++++++++++++++++++++++
>  docs/system/targets.rst             |  1 +
>  5 files changed, 30 insertions(+), 3 deletions(-)
>  rename docs/system/{ => s390x}/vfio-ap.rst (100%)
>  create mode 100644 docs/system/target-s390x.rst

Queued to s390-fixes.



      parent reply	other threads:[~2020-03-18 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 10:39 [PATCH] Documentation: create/move s390x documentation Cornelia Huck
2020-03-18 11:12 ` Peter Maydell
2020-03-18 11:27   ` Cornelia Huck
2020-03-18 12:26 ` Christian Borntraeger
2020-03-18 14:40 ` Cornelia Huck [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=20200318154032.6636c449.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).