qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH memory v1 0/5] MemoryRegion Name QOMification
Date: Thu, 14 Aug 2014 23:53:21 -0700	[thread overview]
Message-ID: <cover.1408085402.git.peter.crosthwaite@xilinx.com> (raw)

Hi Paolo,

Another piece to the Memory Region QOMification puzzle. This series gets
rid of the name field of MemoryRegion and converts all users to the QOM
managed Object name.

Regards,
Peter


Peter Crosthwaite (5):
  loader: Abstract away ref to memory region names
  exec: Abstract away ref to memory region names
  memory: constify memory_region_name
  memory: Use memory_region_name for name access
  memory: Use canonical path component as the name

 exec.c                |  4 ++--
 hw/core/loader.c      |  2 +-
 include/exec/memory.h |  3 +--
 memory.c              | 14 ++++++--------
 4 files changed, 10 insertions(+), 13 deletions(-)

-- 
2.0.1.1.gfbfc394

             reply	other threads:[~2014-08-15  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  6:53 Peter Crosthwaite [this message]
2014-08-15  6:53 ` [Qemu-devel] [PATCH memory v1 1/5] loader: Abstract away ref to memory region names Peter Crosthwaite
2014-08-15  6:54 ` [Qemu-devel] [PATCH memory v1 2/5] exec: " Peter Crosthwaite
2014-08-15  6:55 ` [Qemu-devel] [PATCH memory v1 3/5] memory: constify memory_region_name Peter Crosthwaite
2014-08-15  6:55 ` [Qemu-devel] [PATCH memory v1 4/5] memory: Use memory_region_name for name access Peter Crosthwaite
2014-08-15  6:56 ` [Qemu-devel] [PATCH memory v1 5/5] memory: Use canonical path component as the name Peter Crosthwaite
2014-08-17 20:43 ` [Qemu-devel] [PATCH memory v1 0/5] MemoryRegion Name QOMification 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=cover.1408085402.git.peter.crosthwaite@xilinx.com \
    --to=peter.crosthwaite@xilinx.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).