From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
Bernhard Beschow <shentey@gmail.com>
Cc: qemu-devel@nongnu.org, Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
qemu-ppc@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v4 0/7] Pegasos2 fixes and audio output support
Date: Mon, 27 Feb 2023 23:12:46 +0100 [thread overview]
Message-ID: <b4b60712-a94c-69f4-2de0-b9b5e08970fc@linaro.org> (raw)
In-Reply-To: <2952e466-98e1-cf16-b8c2-fdc49d0ebf48@eik.bme.hu>
On 27/2/23 18:47, BALATON Zoltan wrote:
> On Mon, 27 Feb 2023, Bernhard Beschow wrote:
>> Unfortunately my patches had changes merged in. This now makes it hard to
>> show what really changed (spoiler: nothing that affects behavior).
>>
>> As you probably noticed in the "resend" version of this iteration I split
>> off a patch introducing the priq properties. It belongs to the sub series
>> of the Pegasos2 IRQ fixes which appear unnecessary to me, so I don't want
>> to show up in `git blame` as the author of any of these changes. I
>> attributed it to you because this was really your change which I'm not
>> even
>> sure is legal.
>>
>> Let's avoid such complications by keeping our series separate.
>
> Let's cool down a bit. Philippe took some of the sm501 patches in his
> giant pull request (and a lot of your patches too) now so I'll wait
> until that lands and hope to get some review for the remaining patches
> too. Once that pull req is merged I'll rebase the remaining patches and
> resubmit the series also adding changes for reasonable review comments I
> get by then.
I'm sorry it took me so long, I was expecting these patches to be picked
up by other maintainers but everybody is very busy. I know you'll need
to rebase and it might be painful. But I did that believing it is the
best I could give to the project with my current capacity. Also I don't
want to overlap (too much) into other (sub)maintained areas.
If you are stuck with a rebase, I can try to help.
We'll get to the end of PIIX, if this isn't this release, it will be
the next one. I've been waiting for these cleanups since 4 years
already, before Hervé Poussineau pushed toward that direction during
3 years. We always hit problems due to PC world inheritance which,
as a production system, can not regress.
Also I don't want to compete with you guys, I'd really love to work
together as team, but I have other responsibilities and sometime I
can't spend the time I'd like here.
What blocks the PIIX changes is the "q35/ich9/-device piix3" broken
config. I'll explain elsewhere why it is broken. The problem is I
don't know how to suggest alternative.
Bernhard sometimes it is easier to share visions in a 30min call,
rather than on a such thread. If you want I'm open for one.
next prev parent reply other threads:[~2023-02-27 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 12:57 [PATCH v4 0/7] Pegasos2 fixes and audio output support Bernhard Beschow
2023-02-27 12:57 ` [PATCH v4 1/7] hw/display/sm501: Implement more 2D raster operations Bernhard Beschow
2023-02-27 12:57 ` [PATCH v4 2/7] hw/display/sm501: Add fallbacks to pixman routines Bernhard Beschow
2023-02-27 12:57 ` [PATCH v4 3/7] hw/display/sm501: Add debug property to control pixman usage Bernhard Beschow
2023-02-27 13:00 ` [PATCH v4 0/7] Pegasos2 fixes and audio output support BALATON Zoltan
2023-02-27 13:16 ` Bernhard Beschow
2023-02-27 13:45 ` BALATON Zoltan
2023-02-27 14:35 ` Bernhard Beschow
2023-02-27 16:58 ` BALATON Zoltan
2023-03-01 17:14 ` Mark Cave-Ayland
2023-03-01 18:17 ` BALATON Zoltan
2023-02-27 17:47 ` BALATON Zoltan
2023-02-27 22:12 ` Philippe Mathieu-Daudé [this message]
2023-02-28 8:02 ` Bernhard Beschow
2023-02-28 15:05 ` BALATON Zoltan
2023-02-28 16:25 ` Daniel P. Berrangé
2023-02-28 17:14 ` BALATON Zoltan
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=b4b60712-a94c-69f4-2de0-b9b5e08970fc@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.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).