From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, ian.campbell@eu.citrix.com
Subject: [PATCH v4] Documentation to various header files (v4?).
Date: Fri, 15 Mar 2013 15:51:50 -0400 [thread overview]
Message-ID: <1363377116-30324-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey Ian,
I think this is the last posting of these? I believe we are just
waiting for Jan to Ack the:
[PATCH 5/6] docs: Document start_info changes in Xen 4.2.
and otherwise they are ready to go?
xen/include/public/elfnote.h | 6 ++++++
xen/include/public/features.h | 14 ++++++++++++++
xen/include/public/io/xs_wire.h | 5 ++++-
xen/include/public/xen.h | 22 ++++++++++++++++++++--
4 files changed, 44 insertions(+), 3 deletions(-)
Konrad Rzeszutek Wilk (6):
docs: Document the ELF_FEATURES entry
docs: Add some extra details to the ELF note.
docs: Document the shared structure.
docs: Document the dom0_vga_console_info structure.
docs: Document start_info changes in Xen 4.2.
docs: Document the XenBus structure.
next reply other threads:[~2013-03-15 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:51 Konrad Rzeszutek Wilk [this message]
2013-03-15 19:51 ` [PATCH 1/6] docs: Document the ELF_FEATURES entry Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 2/6] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 3/6] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 4/6] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 5/6] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-03-18 10:55 ` Jan Beulich
2013-03-18 11:11 ` Keir Fraser
2013-03-18 13:08 ` Jan Beulich
2013-03-15 19:51 ` [PATCH 6/6] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-03-18 9:44 ` [PATCH v4] Documentation to various header files (v4?) Ian Campbell
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=1363377116-30324-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).