All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL] hw/ reorganization part 2
Date: Tue, 09 Apr 2013 16:07:00 +0200	[thread overview]
Message-ID: <51642084.6000401@redhat.com> (raw)
In-Reply-To: <CAFEAcA--p4PGGpFkNTAh3y-n+ex+jaQwAQA53f+ibtUC4eCs=Q@mail.gmail.com>

Il 09/04/2013 15:40, Peter Maydell ha scritto:
>> >  {hw => include/hw/arm}/devices.h                   |   0
> Just noticed this is wrong -- devices.h contains prototypes
> for various miscellaneous devices. For instance sm501
> is sh4. This doesn't belong in include/hw/arm/.

I can fix these in a followup.  I saw you also pointed to include/hw/arm.h.

> (More generally I don't much like the include/hw/$ARCH/
> directories -- ideally all these headers should be
> replaced by generic manipulations of properties...)

Yes, they should.

Paolo

      reply	other threads:[~2013-04-09 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 17:30 [Qemu-devel] [PULL] hw/ reorganization part 2 Paolo Bonzini
2013-04-08 21:55 ` Anthony Liguori
2013-04-09 13:40 ` Peter Maydell
2013-04-09 14:07   ` Paolo Bonzini [this message]

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=51642084.6000401@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.