|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v7 2/9] xen/common: Move Arm's bootfdt.c to common
On 05/08/2024 11:04, oleksii.kurochko@xxxxxxxxx wrote: Hi Julien, Hi Oleksii, On Mon, 2024-08-05 at 10:31 +0100, Julien Grall wrote:Hi Oleksii, On 24/07/2024 16:31, Oleksii Kurochko wrote:From: Shawn Anastasio <sanastasio@xxxxxxxxxxxxxxxxxxxxx> Move Arm's bootfdt.c to xen/common so that it can be used by other device tree architectures like PPC and RISCV. Suggested-by: Julien Grall <julien@xxxxxxx> Signed-off-by: Shawn Anastasio <sanastasio@xxxxxxxxxxxxxxxxxxxxx> Acked-by: Julien Grall <julien@xxxxxxx>On Matrix you asked me to review this patch again. This wasn't obvious given you kept my ack. If you think a review is needed, then please either drop the ack or explain why you keep it and ask if it is fine. Also, I tend to list in the changes where this was acked. In this case, you said I acked v4. Anyway, before confirming my ack, I would like to ask some clarification.Signed-off-by: Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx> --- Changes in V7: - Nothing changed. Only rebase. --- Changes in V6: - update the version of the patch to v6. --- Changes in V5: - add xen/include/xen/bootfdt.h to MAINTAINERS file.I don't see any change in MAINTAINERS within this patch. Did you happen to copy/paste all the changes made in the series?This change should be mentioned in this patch. It is part of the previous patch ( https://lore.kernel.org/xen-devel/102f8b60c55cdf2db5890b9fb1c2fb66e61c4a67.1721834549.git.oleksii.kurochko@xxxxxxxxx/ )In fact the only change related to this patch doesn't seem to be listed. [...] With this proposal, you would not throw an error if the user specify "xen,domain-shared-memory-v1" but Xen is not able to support it. This will be a change of behavior for Arm. So my preferred approach is to stick with the existing patch and an explanation in the commit message. Cheers, -- Julien Grall
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |