qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] omap l4 updates
Date: Thu, 24 Nov 2011 17:56:59 +0200	[thread overview]
Message-ID: <1322150222-12869-1-git-send-email-avi@redhat.com> (raw)

The following three patches are part of the memory API conversion queue;
while I don't think there's anything contentious in there, it's not the usual
convert-to-memory-API fare.

The patches remove a bunch of dead code that has not been in use for more
than three years, so they should be quite safe.

Avi Kivity (3):
  omap: remove L4_MUX_HACK
  omap: eliminate l4_register_io_memory
  omap_l4: add memory API variant of omap_l4_attach()

 hw/omap.h           |   12 ++--
 hw/omap2.c          |   14 ++--
 hw/omap_dss.c       |   16 +++---
 hw/omap_gptimer.c   |    4 +-
 hw/omap_i2c.c       |    4 +-
 hw/omap_l4.c        |  159 ++++++++++-----------------------------------------
 hw/omap_mmc.c       |    4 +-
 hw/omap_spi.c       |    4 +-
 hw/omap_synctimer.c |    5 +-
 hw/omap_tap.c       |    5 +-
 10 files changed, 65 insertions(+), 162 deletions(-)

-- 
1.7.7.1

             reply	other threads:[~2011-11-24 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 15:56 Avi Kivity [this message]
2011-11-24 15:57 ` [Qemu-devel] [PATCH 1/3] omap: remove L4_MUX_HACK Avi Kivity
2011-11-27  3:52   ` andrzej zaborowski
2011-11-24 15:57 ` [Qemu-devel] [PATCH 2/3] omap: eliminate l4_register_io_memory Avi Kivity
2011-11-24 15:57 ` [Qemu-devel] [PATCH 3/3] omap_l4: add memory API variant of omap_l4_attach() Avi Kivity
2011-11-27  4:19   ` andrzej zaborowski
2011-11-24 16:22 ` [Qemu-devel] [PATCH 0/3] omap l4 updates Peter Maydell

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=1322150222-12869-1-git-send-email-avi@redhat.com \
    --to=avi@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).