From: John Snow <jsnow@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Floppy <qemu-block@nongnu.org>,
mark.cave-ayland@ilande.co.uk, armbru@redhat.com,
hpoussin@reactos.org, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC for-2.3? 5/8] fdb: Move FDCtrlISABus to header
Date: Tue, 19 May 2015 11:40:43 -0400 [thread overview]
Message-ID: <555B597B.9090307@redhat.com> (raw)
In-Reply-To: <555B3457.4040803@suse.de>
On 05/19/2015 09:02 AM, Andreas Färber wrote:
> Am 31.03.2015 um 03:38 schrieb John Snow:
>> You probably meant 'fdc' !
>>
>> On 03/29/2015 01:53 PM, Andreas Färber wrote:
>>> To be used for embedding the device.
>>>
>>> Add gtk-doc private/public markers for parent field.
>>>
>>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>>> ---
>>> hw/block/fdc.c | 87
>>> -------------------------------------------------
>>> include/hw/block/fdc.h | 88
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 2 files changed, 88 insertions(+), 87 deletions(-)
>
> John, I've rebased this onto the sun4m fdc change. Are you planning to
> take this through your IDE tree or should this go through qom-next?
>
> Regards,
> Andreas
>
I don't need to pick a single patch out of a series because you touch
the FDC stuff, just keep it in-line with the rest of the patches.
I haven't approved anything post-CVE-2015-3456 yet, so as long as you
send the pullreq soon we won't hurt anything*
*Except Kevin's series that he just posted this morning, but I'll deal
with that.
--js
next prev parent reply other threads:[~2015-05-19 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 17:53 [Qemu-devel] [PATCH RFC for-2.3? 0/8] prep: Fix pc87312 for -device usage Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 1/8] parallel: Factor out header for ISAParallelState struct Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 2/8] pc87312: Create isa-parallel in-place and add alias par0-chardev property Andreas Färber
2015-03-30 14:12 ` Markus Armbruster
2015-03-30 14:36 ` Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 3/8] serial: Move ISASerialState to header Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 4/8] pc87312: Create UARTs in-place and add alias properties Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 5/8] fdb: Move FDCtrlISABus to header Andreas Färber
2015-03-31 1:38 ` John Snow
2015-05-19 13:02 ` Andreas Färber
2015-05-19 15:40 ` John Snow [this message]
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 6/8] pc87312: Create FDC in-place Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 7/8] ide: Move ISAIDEState to header Andreas Färber
2015-03-29 17:53 ` [Qemu-devel] [PATCH RFC for-2.3? 8/8] pc87312: Create IDE in-place Andreas Färber
2015-03-30 14:25 ` [Qemu-devel] [PATCH RFC for-2.3? 0/8] prep: Fix pc87312 for -device usage Markus Armbruster
2015-03-30 16:12 ` Paolo Bonzini
2015-03-30 16:18 ` Andreas Färber
2015-03-30 18:09 ` Markus Armbruster
2015-03-30 16:42 ` Markus Armbruster
2015-03-30 17:49 ` Andreas Färber
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=555B597B.9090307@redhat.com \
--to=jsnow@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=hpoussin@reactos.org \
--cc=kwolf@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanha@redhat.com \
/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).