From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] find_ram_offset cleanups and alignment
Date: Fri, 5 Jan 2018 17:01:36 +0000 [thread overview]
Message-ID: <20180105170138.23357-1-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Hi,
This is mainly the alignment change that Paolo asked for
in the 2nd commit, but while I was there I added some comments
and tracing that I've split out.
Dave
Dr. David Alan Gilbert (2):
find_ram_offset: Add comments and tracing
find_ram_offset: Align ram_addr_t allocation on long boundaries
exec.c | 22 +++++++++++++++++++++-
trace-events | 3 +++
2 files changed, 24 insertions(+), 1 deletion(-)
--
2.14.3
next reply other threads:[~2018-01-05 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 17:01 Dr. David Alan Gilbert (git) [this message]
2018-01-05 17:01 ` [Qemu-devel] [PATCH 1/2] find_ram_offset: Add comments and tracing Dr. David Alan Gilbert (git)
2018-01-05 17:20 ` Eric Blake
2018-01-08 22:08 ` Juan Quintela
2018-01-05 17:01 ` [Qemu-devel] [PATCH 2/2] find_ram_offset: Align ram_addr_t allocation on long boundaries Dr. David Alan Gilbert (git)
2018-01-05 17:19 ` Eric Blake
2018-01-08 22:08 ` Juan Quintela
2018-01-10 14:03 ` Paolo Bonzini
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=20180105170138.23357-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).