From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com,
peter.maydell@linaro.org, thuth@redhat.com,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [Qemu-devel] [PATCH v2] Kconfig: add documentation
Date: Tue, 12 Feb 2019 11:28:34 +0100 [thread overview]
Message-ID: <20190212112834.3af78ea2.cohuck@redhat.com> (raw)
In-Reply-To: <20190212095749.20313-1-pbonzini@redhat.com>
On Tue, 12 Feb 2019 10:57:49 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> docs/devel/kconfig.rst | 305 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 305 insertions(+)
> create mode 100644 docs/devel/kconfig.rst
Looks good!
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-02-12 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 9:57 [Qemu-devel] [PATCH v2] Kconfig: add documentation Paolo Bonzini
2019-02-12 10:28 ` Cornelia Huck [this message]
2019-02-12 11:11 ` Liam Merwick
2019-02-13 2:53 ` Peter Xu
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=20190212112834.3af78ea2.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=armbru@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).