qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH qom-next v1 0/6] SSI QOM cleanups
Date: Tue, 25 Feb 2014 09:51:13 +0100	[thread overview]
Message-ID: <530C5981.5010501@suse.de> (raw)
In-Reply-To: <CAEgOgz5xzLKctkzTku5RPgmhmrv=k5x5Wv7TpPW-bR7Lmdk4mA@mail.gmail.com>

Am 25.02.2014 09:46, schrieb Peter Crosthwaite:
> Ping!

Looked good, didn't get to applying them yet. I did wonder though a) why
1/6 is not renaming the parent field to verify and b) whether I can swap
d vs. dev naming in one hunk there while at it.

Cheers,
Andreas

> 
> On Wed, Feb 12, 2014 at 10:27 AM, Peter Crosthwaite
> <peter.crosthwaite@xilinx.com> wrote:
>> Hi Andreas,
>>
>> Here is a mixed bag of QOM cleanups, moving us slightly closer to
>> QOMification of SSI.
>>
>> This prepares support for some major refactoring around SSI (in
>> particular some QSPI patches).
>>
>> Regards,
>> Peter
>>
>>
>> Peter Crosthwaite (6):
>>   ssi: Convert legacy casts from SSI_SLAVE->DEVICE
>>   ssi: Remove legacy SSI_BUS->BUS cast
>>   misc: max111x: Create abstract max111x class
>>   misc: max111x: QOM casting sweep
>>   ssi: Remove SSI_SLAVE_FROM_QDEV macro
>>   block/m25p80: Remove FROM_SSI_SLAVE usages
>>
>>  hw/arm/spitz.c       |  9 +++++----
>>  hw/block/m25p80.c    |  6 +++---
>>  hw/display/ads7846.c |  2 +-
>>  hw/display/ssd0323.c |  4 ++--
>>  hw/misc/max111x.c    | 46 +++++++++++++++++++++++++++++++++-------------
>>  hw/sd/ssi-sd.c       |  2 +-
>>  hw/ssi/ssi.c         |  4 ++--
>>  include/hw/ssi.h     |  1 -
>>  8 files changed, 47 insertions(+), 27 deletions(-)
>>
>> --
>> 1.8.5.4
>>


-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-02-25  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  0:27 [Qemu-devel] [PATCH qom-next v1 0/6] SSI QOM cleanups Peter Crosthwaite
2014-02-12  0:27 ` [Qemu-devel] [PATCH qom-next v1 1/6] ssi: Convert legacy casts from SSI_SLAVE->DEVICE Peter Crosthwaite
2014-03-04 22:07   ` Andreas Färber
2014-03-04 22:23     ` Andreas Färber
2014-02-12  0:28 ` [Qemu-devel] [PATCH qom-next v1 2/6] ssi: Remove legacy SSI_BUS->BUS cast Peter Crosthwaite
2014-03-04 20:43   ` Andreas Färber
2014-02-12  0:29 ` [Qemu-devel] [PATCH qom-next v1 3/6] misc: max111x: Create abstract max111x class Peter Crosthwaite
2014-02-12  0:29 ` [Qemu-devel] [PATCH qom-next v1 4/6] misc: max111x: QOM casting sweep Peter Crosthwaite
2014-03-04 20:51   ` Andreas Färber
2014-02-12  0:30 ` [Qemu-devel] [PATCH qom-next v1 5/6] ssi: Remove SSI_SLAVE_FROM_QDEV macro Peter Crosthwaite
2014-02-12  0:30 ` [Qemu-devel] [PATCH qom-next v1 6/6] block/m25p80: Remove FROM_SSI_SLAVE usages Peter Crosthwaite
2014-03-04 20:57   ` Andreas Färber
2014-02-25  8:46 ` [Qemu-devel] [PATCH qom-next v1 0/6] SSI QOM cleanups Peter Crosthwaite
2014-02-25  8:51   ` Andreas Färber [this message]
2014-03-04 22:39     ` Andreas Färber
2014-03-04 23:32       ` Peter Crosthwaite

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=530C5981.5010501@suse.de \
    --to=afaerber@suse.de \
    --cc=peter.crosthwaite@xilinx.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 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).