[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset
From: |
Blue Swirl |
Subject: |
Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset |
Date: |
Wed, 23 May 2012 18:48:25 +0000 |
On Tue, May 22, 2012 at 12:34 AM, Andreas Färber <address@hidden> wrote:
> Am 21.05.2012 20:20, schrieb Blue Swirl:
>> On Mon, May 21, 2012 at 9:09 AM, Andreas Färber <address@hidden> wrote:
>>> Am 14.05.2012 23:22, schrieb Blue Swirl:
>>>> On Mon, May 14, 2012 at 8:59 PM, Andreas Färber <address@hidden> wrote:
>>>>> Am 14.05.2012 21:54, schrieb Blue Swirl:
>>>>>> On Mon, May 14, 2012 at 4:15 PM, Andreas Färber <address@hidden> wrote:
>>>>>>> Am 10.05.2012 02:13, schrieb Andreas Färber:
>>>>>>>> Andreas Färber (74):
>>>>>>> [...]
>>>>>>>> target-sparc: Let cpu_sparc_init() return SPARCCPU
>>>>>>>> sun4m: Use cpu_sparc_init() to obtain SPARCCPU
>>>>>>>> sun4m: Pass SPARCCPU to {main,secondary}_cpu_reset()
>>>>>>>> sun4u: Use cpu_sparc_init() to obtain SPARCCPU
>>>>>>>> sun4u: Let cpu_devinit() return SPARCCPU
>>>>>>>> sun4u: Store SPARCCPU in ResetData
>>>>>>>> leon3: Use cpu_sparc_init() to obtain SPARCCPU
>>>>>>>> leon3: Store SPARCCPU in ResetData
>>>>>>> [...]
>>>>>
>>>>> Forgot to mention the bsd-user patch.
>>>>>
>>>>>>>> Kill off cpu_state_reset()
>>>>>>>
>>>>>>> Ping! Blue, can you ack please?
>>>>>>
>>>>>> Otherwise the patches look pretty safe ("if it compiles, it works").
>>>
>>> Was I supposed to interpret that as an Acked-by? ;)
>>
>> No, but you may do so if it compiles. ;-)
>
> Joking, are we? My cover letter indicated pretty clearly on what
> platforms I had already compile-tested on, and that meant each patch.
> I had also run `make check` on each and the sparc test image for sun4m,
> HelenOS for sun4u and "crible" for leon3.
OK,
Acked-by: Blue Swirl <address@hidden>
>
> Applied the remainder of the series to qom-next:
> http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-next
>
> Tristan/Fabien, could you please submit a patch to document the Leon3
> machine in MAINTAINERS? No one got cc'ed on those two patches. Thanks.
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
- [Qemu-devel] [PATCH next v2 69/74] mips_mipssim: Store MIPSCPU in ResetData, (continued)
- [Qemu-devel] [PATCH next v2 69/74] mips_mipssim: Store MIPSCPU in ResetData, Andreas Färber, 2012/05/09
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/14
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/14
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Blue Swirl, 2012/05/14
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/14
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Blue Swirl, 2012/05/14
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/21
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Blue Swirl, 2012/05/21
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/21
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Fabien Chouteau, 2012/05/22
- Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset,
Blue Swirl <=
Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Igor Mammedov, 2012/05/15
Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/16
Re: [Qemu-devel] [PATCH next v2 00/74] QOM CPUState, part 3: CPU reset, Andreas Färber, 2012/05/21