From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org, ian.campbell@citrix.com,
ian.jackson@eu.citrix.com, jbeulich@suse.com, tim@xen.org,
keir@xen.org
Subject: [PATCH] Various fixes - libelf, paging, blktap.
Date: Sat, 3 Oct 2015 14:39:47 -0400 [thread overview]
Message-ID: <1443897590-5663-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey,
I was working on xSplice I enabled various options which ended
up causing compiler issues (except the first one).
The:
[PATCH v1 1/3] libelf: Preserve log callback after elf_init
was a result of trying to use the libelf in some user-space and
messing up badly but not getting any errors because libelf would
'forget' the log callback.
The other two:
[PATCH v1 2/3] paging: Fix compile error when DEBUG_TRACE_DUMP is
[PATCH v1 3/3] blktap2: Silence warnings under GCC 5.1.1
Are just fixes for compiler issues.
tools/blktap2/drivers/block-log.c | 4 ++--
xen/arch/x86/mm/paging.c | 4 ++--
xen/common/libelf/libelf-loader.c | 16 +++++++++++++++-
3 files changed, 19 insertions(+), 5 deletions(-)
Konrad Rzeszutek Wilk (3):
libelf: Preserve log callback after elf_init
paging: Fix compile error when DEBUG_TRACE_DUMP is enabled.
blktap2: Silence warnings under GCC 5.1.1
next reply other threads:[~2015-10-03 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 18:39 Konrad Rzeszutek Wilk [this message]
2015-10-03 18:39 ` [PATCH v1 1/3] libelf: Preserve log callback after elf_init Konrad Rzeszutek Wilk
2015-10-05 10:36 ` Jan Beulich
2015-10-05 14:23 ` Konrad Rzeszutek Wilk
2015-10-05 14:39 ` Jan Beulich
2015-10-05 14:48 ` Konrad Rzeszutek Wilk
2015-10-03 18:39 ` [PATCH v1 2/3] paging: Fix compile error when DEBUG_TRACE_DUMP is enabled Konrad Rzeszutek Wilk
2015-10-05 8:46 ` Andrew Cooper
2015-10-03 18:39 ` [PATCH v1 3/3] blktap2: Silence warnings under GCC 5.1.1 Konrad Rzeszutek Wilk
2015-10-05 8:49 ` Andrew Cooper
2015-10-05 10:46 ` Jan Beulich
2015-10-05 14:26 ` Konrad Rzeszutek Wilk
2015-10-05 14:46 ` Jan Beulich
2015-10-05 14:57 ` Konrad Rzeszutek Wilk
2015-10-05 15:02 ` Jan Beulich
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=1443897590-5663-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).