From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] docs/traces Acked patches.
Date: Wed, 27 Mar 2013 12:36:56 -0400 [thread overview]
Message-ID: <20130327163656.GA8940@phenom.dumpdata.com> (raw)
In-Reply-To: <20817.52407.779788.264328@mariner.uk.xensource.com>
On Tue, Mar 26, 2013 at 04:28:39PM +0000, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("[PATCH] docs/traces Acked patches. "):
> > Please commit these patches. I can also put these on a git tree
> > (if you could create on for me on xenbits.org that is it) for a git pull.
>
> Please do put them in a git tree. You can make one yourself using
> your shell account on xenbits.
Done.
Please git pull the following branch:
git://xenbits.xen.org/people/konradwilk/xen.git docs.v3
which has these patches since git commit babea0a412ee24a94ed0bd03543060b2c6bc0bbd
(trace: Add reason for NMI exit TRAP):
xen/include/public/elfnote.h | 8 ++++++++
xen/include/public/features.h | 14 ++++++++++++++
xen/include/public/io/xs_wire.h | 5 ++++-
xen/include/public/xen.h | 22 ++++++++++++++++++++--
4 files changed, 46 insertions(+), 3 deletions(-)
Konrad Rzeszutek Wilk (7):
docs: Document the ELF notes
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.
Thank you.
next prev parent reply other threads:[~2013-03-27 16:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 14:41 [PATCH] docs/traces Acked patches Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 01/11] trace: Use correct trace class for power management changes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 02/11] trace: Add trace events for IRQ activities Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 03/11] trace: Add the other variant of do_block Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 04/11] trace: Add reason for NMI exit TRAP Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 05/11] docs: Document the ELF notes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 06/11] docs: Document the ELF_FEATURES entry Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 07/11] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 08/11] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 09/11] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 10/11] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 11/11] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-03-25 15:13 ` [PATCH] docs/traces Acked patches Jan Beulich
2013-03-25 15:37 ` George Dunlap
2013-03-25 15:48 ` Jan Beulich
2013-03-25 16:43 ` George Dunlap
2013-03-25 19:57 ` Konrad Rzeszutek Wilk
2013-03-25 16:46 ` Konrad Rzeszutek Wilk
2013-03-25 17:20 ` Jan Beulich
2013-03-25 20:04 ` Konrad Rzeszutek Wilk
2013-04-10 9:24 ` Ian Campbell
2013-03-26 16:28 ` Ian Jackson
2013-03-27 16:36 ` Konrad Rzeszutek Wilk [this message]
2013-03-28 16:00 ` Ian Jackson
2013-03-29 13:06 ` Konrad Rzeszutek Wilk
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=20130327163656.GA8940@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.