From: "Andreas Färber" <afaerber@suse.de>
To: Alberto Garcia <agarcia@igalia.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Paul Brook <paul@codesourcery.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Ping [PATCH 0/2] Add TPCI200 and IP-Octal 232 IndustryPack emulation
Date: Fri, 05 Oct 2012 16:54:03 +0200 [thread overview]
Message-ID: <506EF48B.5070002@suse.de> (raw)
In-Reply-To: <20121005132036.GA29555@igalia.com>
Am 05.10.2012 15:20, schrieb Alberto Garcia:
> On Fri, Aug 31, 2012 at 06:09:11PM +0200, Andreas Färber wrote:
>
>>> Ping
>>
>> We are currently in Hard Freeze, new devices will not get accepted
>> before the release, and our review may focus on bug fixes.
>>
>> http://wiki.qemu.org/Planning/1.2
>>
>> I remember having had a brief look through your patches and
>> they looked pretty good modeling- and style-wise for an initial
>> submission. Don't know the hardware though and haven't tested the
>> patches so far.
>
> I wrote a small blog post about the work, including a bit more
> information on how to test it:
>
> http://blogs.igalia.com/berto/2012/10/03/industrypack-qemu-and-linuxcon/
Thanks for the illustrative blog post.
One thing caught my eye: Wouldn't it make more sense to call the device
"ipoctal232"? Octal doesn't indicate of what there are eight. ;)
> Is there anything else I should do in order to have this reviewed, or
> should I contact someone else?
Paul and Peter are the ones with experience reviewing UARTs, I think.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-10-05 14:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:59 [Qemu-devel] [PATCH 0/2] Add TPCI200 and IP-Octal 232 IndustryPack emulation Alberto Garcia
2012-08-23 13:59 ` [Qemu-devel] [PATCH 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-08-23 13:59 ` [Qemu-devel] [PATCH 2/2] Add IP-Octal 232 " Alberto Garcia
2012-08-31 14:12 ` [Qemu-devel] Ping [PATCH 0/2] Add TPCI200 and " Alberto Garcia
2012-08-31 16:09 ` Andreas Färber
2012-09-10 13:10 ` Alberto Garcia
2012-10-05 13:20 ` Alberto Garcia
2012-10-05 14:28 ` Paolo Bonzini
2012-10-05 14:52 ` Anthony Liguori
2012-10-05 16:24 ` Blue Swirl
2012-10-06 11:29 ` Alberto Garcia
2012-10-07 10:13 ` Avi Kivity
2012-10-07 10:19 ` Avi Kivity
2012-10-08 8:02 ` Alberto Garcia
2012-10-10 10:24 ` Alberto Garcia
2012-10-10 11:35 ` Avi Kivity
2012-10-10 17:59 ` Alberto Garcia
2012-10-05 14:54 ` Andreas Färber [this message]
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 " Alberto Garcia
2012-12-05 14:03 ` Andreas Färber
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 2/2] Add GE IP-Octal 232 " Alberto Garcia
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 0/2] Add TPCI200 and " Alberto Garcia
2012-12-17 15:27 ` [Qemu-devel] Ping " Alberto Garcia
2013-01-07 20:32 ` Anthony Liguori
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 2/2] Add GE IP-Octal 232 " Alberto Garcia
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=506EF48B.5070002@suse.de \
--to=afaerber@suse.de \
--cc=agarcia@igalia.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=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 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).