[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [PATCH v3 4/5] arm: boot: set boot_info starting from fir
From: |
Igor Mammedov |
Subject: |
Re: [Qemu-arm] [PATCH v3 4/5] arm: boot: set boot_info starting from first_cpu |
Date: |
Tue, 1 May 2018 15:34:11 +0200 |
On Tue, 1 May 2018 13:19:12 +0100
Peter Maydell <address@hidden> wrote:
> On 1 May 2018 at 13:08, Igor Mammedov <address@hidden> wrote:
> > even though nothing is currently broken, make sure that boot_info
> > is set on all CPUs.
> >
> > Ref:
> > "Message-ID: <address@hidden>"
>
> Can you include the rationale in the commit message rather
> than just pointing to a message-id, please?
sure,
I'll post it reply here.
BTW: I'm expecting this being merged through ARM tree
> >
> > Signed-off-by: Igor Mammedov <address@hidden>
> > --
>
> Otherwise
> Reviewed-by: Peter Maydell <address@hidden>
>
> thanks
> -- PMM
- [Qemu-arm] [PATCH v3 0/5] arm: isolate and clean up dtb generation, Igor Mammedov, 2018/05/01
- [Qemu-arm] [PATCH v3 2/5] platform-bus-device: use device plug callback instead of machine_done notifier, Igor Mammedov, 2018/05/01
- [Qemu-arm] [PATCH v3 1/5] pc: simplify MachineClass::get_hotplug_handler handling, Igor Mammedov, 2018/05/01
- [Qemu-arm] [PATCH v3 4/5] arm: boot: set boot_info starting from first_cpu, Igor Mammedov, 2018/05/01
- [Qemu-arm] [PATCH v3 3/5] arm/boot: split load_dtb() from arm_load_kernel(), Igor Mammedov, 2018/05/01
- [Qemu-arm] [PATCH v3 5/5] make sure that we aren't overwriting mc->get_hotplug_handler by accident, Igor Mammedov, 2018/05/01
- Re: [Qemu-arm] [PATCH v3 0/5] arm: isolate and clean up dtb generation, Peter Maydell, 2018/05/03