From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/3] QOM devices patch queue 2014-11-04
Date: Tue, 4 Nov 2014 18:42:51 +0000 [thread overview]
Message-ID: <CAFEAcA-571SQ7y29fkZ6Hee727gqkjH-bsL4ST_mqc_XA78djQ@mail.gmail.com> (raw)
In-Reply-To: <1415122209-29164-1-git-send-email-afaerber@suse.de>
On 4 November 2014 17:30, Andreas Färber <afaerber@suse.de> wrote:
> Hello Peter,
>
> This is my QOM (devices) patch queue. Please pull.
>
> Regards,
> Andreas
>
> Cc: Peter Maydell <peter.maydell@linaro.org>
>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
>
> The following changes since commit 1bc8dae31baa8b02a1b8e70c3244232e03bbb3b2:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/pull-gtk-20141104-2' into staging (2014-11-04 15:00:17 +0000)
>
> are available in the git repository at:
>
>
> git://github.com/afaerber/qemu-cpu.git tags/qom-devices-for-peter
>
> for you to fetch changes up to 31bed5509dfcbdfc293154ce81086a4dbd7a80b6:
>
> qdev: Use qdev_get_device_class() for -device <type>,help (2014-11-04 17:50:00 +0100)
>
> ----------------------------------------------------------------
> QOM infrastructure fixes and device conversions
>
> * Fixes for -device foo,help
>
> ----------------------------------------------------------------
Applied, thanks.
-- PMM
prev parent reply other threads:[~2014-11-04 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 17:30 [Qemu-devel] [PULL 0/3] QOM devices patch queue 2014-11-04 Andreas Färber
2014-11-04 17:30 ` [Qemu-devel] [PULL 1/3] qdev: Create qdev_get_device_class() function Andreas Färber
2014-11-04 17:30 ` [Qemu-devel] [PULL 2/3] qdev: Move error printing to the end of qdev_device_help() Andreas Färber
2014-11-04 17:30 ` [Qemu-devel] [PULL 3/3] qdev: Use qdev_get_device_class() for -device <type>, help Andreas Färber
2014-11-04 18:42 ` Peter Maydell [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=CAFEAcA-571SQ7y29fkZ6Hee727gqkjH-bsL4ST_mqc_XA78djQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=ehabkost@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).