Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-04-01 Thread Anthony Liguori
Applied. Thanks. Regards, Anthony Liguori

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Peter Maydell
On 28 March 2013 15:56, Anthony Liguori wrote: > I'll apply these.. In the future, please CC me when sending patches > like this. Yes, I tend to forget to CC you on general type patches (as opposed to ones where you're specifically a maintainer for the area); hence the ping with you added to the

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Anthony Liguori
Peter Maydell writes: > On 28 March 2013 15:15, Andreas Färber wrote: >> Am 28.03.2013 12:25, schrieb Peter Maydell: >>> Ping! >> >> All patches have at least one Reviewed-by or Acked-by including that of >> the lm32 maintainer, so you could just apply these to arm-devs.next, no? > > Well, I cou

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Paolo Bonzini
> On 28 March 2013 15:15, Andreas Färber wrote: > > Am 28.03.2013 12:25, schrieb Peter Maydell: > >> Ping! > > > > All patches have at least one Reviewed-by or Acked-by including > > that of > > the lm32 maintainer, so you could just apply these to > > arm-devs.next, no? > > Well, I could, but t

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Peter Maydell
On 28 March 2013 15:15, Andreas Färber wrote: > Am 28.03.2013 12:25, schrieb Peter Maydell: >> Ping! > > All patches have at least one Reviewed-by or Acked-by including that of > the lm32 maintainer, so you could just apply these to arm-devs.next, no? Well, I could, but they're not really arm pat

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Andreas Färber
Am 28.03.2013 12:25, schrieb Peter Maydell: > Ping! All patches have at least one Reviewed-by or Acked-by including that of the lm32 maintainer, so you could just apply these to arm-devs.next, no? Andreas > > -- PMM > > On 15 March 2013 14:34, Peter Maydell wrote: >> The functions sysbus_add_

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-28 Thread Peter Maydell
Ping! -- PMM On 15 March 2013 14:34, Peter Maydell wrote: > The functions sysbus_add_memory and sysbus_del_memory are odd wrappers > around around memory_region_add/del_subregion, and their presence > is an encouragement to devices to try to map their own memory > regions into the system address

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-15 Thread Paolo Bonzini
Il 15/03/2013 17:09, Peter Maydell ha scritto: > On 15 March 2013 16:00, Paolo Bonzini wrote: >> Il 15/03/2013 15:34, Peter Maydell ha scritto: >>> I rather suspect sysbus_add_io and sysbus_del_io should also be >>> removed, but since their users are in PPC and x86 platforms I'll >>> let somebody

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-15 Thread Peter Maydell
On 15 March 2013 16:00, Paolo Bonzini wrote: > Il 15/03/2013 15:34, Peter Maydell ha scritto: >> I rather suspect sysbus_add_io and sysbus_del_io should also be >> removed, but since their users are in PPC and x86 platforms I'll >> let somebody else do that part :-) > > sysbus_add_io and sysbus_de

Re: [Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-15 Thread Paolo Bonzini
Il 15/03/2013 15:34, Peter Maydell ha scritto: > I rather suspect sysbus_add_io and sysbus_del_io should also be > removed, but since their users are in PPC and x86 platforms I'll > let somebody else do that part :-) sysbus_add_io and sysbus_del_io are actually a good match for the I/O address spa

[Qemu-devel] [PATCH v3 0/5] Remove sysbus_add_memory and sysbus_del_memory

2013-03-15 Thread Peter Maydell
The functions sysbus_add_memory and sysbus_del_memory are odd wrappers around around memory_region_add/del_subregion, and their presence is an encouragement to devices to try to map their own memory regions into the system address space. Since they're only used in a couple of places in the milkymi