qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: Scott Wood <scottwood@freescale.com>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] macio: Convert to realize()
Date: Sat, 16 May 2015 14:42:35 +0200	[thread overview]
Message-ID: <55573B3B.1030800@suse.de> (raw)
In-Reply-To: <87pp629csz.fsf@blackfin.pond.sub.org>



On 15.05.15 15:43, Markus Armbruster wrote:
> Alexander Graf <agraf@suse.de> writes:
> 
>> On 17.03.15 08:46, Markus Armbruster wrote:
>>> Alexander Graf <agraf@suse.de> writes:
>>>
>>>> On 09.03.15 19:30, Markus Armbruster wrote:
>>>>> Alexander Graf <agraf@suse.de> writes:
>>>>>
>>>>>> On 27.02.15 13:43, Markus Armbruster wrote:
>>>>>>> Convert device models "macio-oldworld" and "macio-newworld".
>>>>>>>
>>>>>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>>>>>> ---
>>>>>>> Depends on my "[PATCH 00/10] pci: Partial conversion to realize",
>>>>>>> which is in Michael's latest pull request.
>>>>>>
>>>>>> Can you please poke me again when it landed?
>>>>>
>>>>> Applies cleanly to master now (commit 277263e).
>>>>
>>>> Hrm, does not seem to apply cleanly now. How about we postpone this to
>>>> 2.4? It's not really crucial for 2.3 and we're in hard freeze now.
>>>
>>> Sad (it's been on list for almost three weeks, most of the time waiting
>>> for the PCI pull), but it's clearly your choice to make.
>>
>> Yeah, but we're past hard freeze and I'd consider this not critical
>> enough to warrant potential breakage.
>>
>>> git-am doesn't dare to apply the patch on list, but git-cherry-pick
>>> applies the commit from which it was formatted without a peep.  Result
>>> appended, just in case you'd like to consider it.
>>
>> Awesome, that was quick. Thanks, applied to ppc-next-2.4.
> 
> Pull request ETA?  I don't mean to be pushy, but I've been trying to get
> this in since February, and I got more work depending on it...

Some of the patches in David's latest spapr queue are regressing
compilation on older libfdt versions right now. If I don't see patches
to fix this, I'll just remove them from my queue again.

I could also use some help triaging the current autotest failures:

  https://lists.gnu.org/archive/html/qemu-ppc-autotest/2015-05/msg00003.html

A good amount of those is probably upstream kernel breakage, but it'd be
good to know for sure.


Alex

  reply	other threads:[~2015-05-16 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 12:43 [Qemu-devel] [PATCH] macio: Convert to realize() Markus Armbruster
2015-02-27 14:55 ` Alexander Graf
2015-02-27 15:26   ` Markus Armbruster
2015-03-09 18:30   ` Markus Armbruster
2015-03-17  7:26     ` Alexander Graf
2015-03-17  7:46       ` Markus Armbruster
2015-03-17  7:50         ` Alexander Graf
2015-05-15 13:43           ` Markus Armbruster
2015-05-16 12:42             ` Alexander Graf [this message]
2015-05-18  7:11               ` Thomas Huth
2015-05-18  8:59                 ` Peter Maydell
2015-05-18  9:28                   ` Thomas Huth

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=55573B3B.1030800@suse.de \
    --to=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.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).