From: Peter Maydell <peter.maydell@linaro.org>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: "Edgar Iglesias" <edgar.iglesias@xilinx.com>,
"Edgar Iglesias" <edgar.iglesias@gmail.com>,
"Peter Crosthwaite" <crosthwaitepeter@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v1 00/15] data-driven device registers
Date: Fri, 8 Jan 2016 10:40:28 +0000 [thread overview]
Message-ID: <CAFEAcA9-gtY5GHS6Fjd2DcgvaginkknmuauseY-NkVwkjMecfQ@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKO5jXcsir8ME5X4ypgh0NAWu5af+D68AxtrbrVnjYZWpQ@mail.gmail.com>
On 8 January 2016 at 00:39, Alistair Francis
<alistair.francis@xilinx.com> wrote:
> On Wed, Dec 16, 2015 at 8:33 AM, Alistair Francis
> <alistair.francis@xilinx.com> wrote:
>> On Tue, Dec 15, 2015 at 1:56 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> On 15 December 2015 at 20:52, Peter Crosthwaite
>>> <crosthwaitepeter@gmail.com> wrote:
>>>> It needs to exist before it can be used so there is a bit of a chicken
>>>> and egg problem there.
>
> No one seems to be jumping at reviewing this. Can we just send a pull request?
I don't necessarily require review [*]. I would like *somebody* other
than you Xilinx folk to say "yes, I think I would use this for
modelling devices". Otherwise all we have is "weird thing used
only in two or three Xilinx devices and nowhere else", which I'm
a bit reluctant to let into the tree. We already have a pretty
wide divergence in how devices look just based on the various
transitions from older to newer qdev/QOM/etc that are not complete.
[*] by which I mean, I will review this series if you can find
somebody else who's going to say they'd use it.
thanks
-- PMM
next prev parent reply other threads:[~2016-01-08 10:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 20:24 [Qemu-devel] [PATCH v1 00/15] data-driven device registers Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 01/15] register: Add Register API Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 02/15] register: Add Memory API glue Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 03/15] register: Add support for decoding information Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 04/15] register: Define REG and FIELD macros Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 05/15] register: QOMify Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 06/15] register: Add block initialise helper Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 07/15] bitops: Add ONES macro Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 08/15] dma: Add Xilinx Zynq devcfg device model Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 09/15] xilinx_zynq: add devcfg to machine model Alistair Francis
2015-07-29 20:24 ` [Qemu-devel] [PATCH v1 10/15] qdev: Define qdev_get_gpio_out Alistair Francis
2015-07-29 20:25 ` [Qemu-devel] [PATCH v1 11/15] qdev: Add qdev_pass_all_gpios API Alistair Francis
2015-07-29 20:25 ` [Qemu-devel] [PATCH v1 12/15] irq: Add opaque setter routine Alistair Francis
2015-07-29 20:25 ` [Qemu-devel] [PATCH v1 13/15] register: Add GPIO API Alistair Francis
2015-07-29 20:25 ` [Qemu-devel] [PATCH v1 14/15] misc: Introduce ZynqMP IOU SLCR Alistair Francis
2015-07-29 20:25 ` [Qemu-devel] [PATCH v1 15/15] xlnx-zynqmp: Connect the " Alistair Francis
2015-08-27 21:47 ` [Qemu-devel] [PATCH v1 00/15] data-driven device registers Alistair Francis
2015-10-14 18:42 ` Alistair Francis
2015-10-30 6:52 ` Peter Crosthwaite
2015-10-30 8:06 ` Peter Maydell
2015-12-15 19:46 ` Peter Maydell
2015-12-15 20:52 ` Peter Crosthwaite
2015-12-15 21:56 ` Peter Maydell
2015-12-16 16:33 ` Alistair Francis
2016-01-08 0:39 ` Alistair Francis
2016-01-08 10:40 ` Peter Maydell [this message]
2016-01-08 11:05 ` Edgar E. Iglesias
2016-01-19 19:51 ` Alistair Francis
2016-01-19 21:35 ` Edgar E. Iglesias
2016-01-28 16:31 ` Frederic Konrad
2016-01-28 16:34 ` Peter Maydell
2016-01-30 0:56 ` Alistair Francis
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=CAFEAcA9-gtY5GHS6Fjd2DcgvaginkknmuauseY-NkVwkjMecfQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaitepeter@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.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).