On 10/6/20 11:54 AM, Paolo Bonzini wrote:
> On 06/10/20 11:43, BALATON Zoltan wrote:
>>
>> The name of this dir may be misleading. I think it originally stood
>> for the actual MMU emulation but now it seems everything related to
>> system emulation is dumped here. Is it better to keep MMU
On 06/10/20 11:43, BALATON Zoltan wrote:
>
> The name of this dir may be misleading. I think it originally stood
> for the actual MMU emulation but now it seems everything related to
> system emulation is dumped here. Is it better to keep MMU emulation
> separate and put other files in a "sysemu"
On Tue, 6 Oct 2020, Paolo Bonzini wrote:
Keep most softmmu_ss files into the system-emulation-specific
directory.
The name of this dir may be misleading. I think it originally stood for
the actual MMU emulation but now it seems everything related to system
emulation is dumped here. Is it
On 10/6/20 11:34 AM, Philippe Mathieu-Daudé wrote:
> On 10/6/20 11:19 AM, Paolo Bonzini wrote:
>> Keep most softmmu_ss files into the system-emulation-specific
>> directory.
Oops, you forgot to update MAINTAINERS.
>>
>> Signed-off-by: Paolo Bonzini
>> ---
>> meson.build
On 10/6/20 11:19 AM, Paolo Bonzini wrote:
> Keep most softmmu_ss files into the system-emulation-specific
> directory.
>
> Signed-off-by: Paolo Bonzini
> ---
> meson.build | 10 --
> bootdevice.c => softmmu/bootdevice.c | 0
> device_tree.c =>
Keep most softmmu_ss files into the system-emulation-specific
directory.
Signed-off-by: Paolo Bonzini
---
meson.build | 10 --
bootdevice.c => softmmu/bootdevice.c | 0
device_tree.c => softmmu/device_tree.c | 0
dma-helpers.c =>
