[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20220523163040.6064b190@canb.auug.org.au>
Date: Mon, 23 May 2022 16:30:40 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Juergen Gross <jgross@...e.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Xen Devel <xen-devel@...ts.xenproject.org>,
Dmitry Osipenko <dmitry.osipenko@...labora.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Maximilian Heyne <mheyne@...zon.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: linux-next: manual merge of the xen-tip tree with the pm tree
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/xen/enlighten_pv.c
between commit:
f089ab674cea ("xen/x86: Use do_kernel_power_off()")
from the pm tree and commit:
1591a65f55bc ("x86: xen: remove STACK_FRAME_NON_STANDARD from xen_cpuid")
from the xen-tip tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/x86/xen/enlighten_pv.c
index af1f6e886225,ca85d1409917..000000000000
--- a/arch/x86/xen/enlighten_pv.c
+++ b/arch/x86/xen/enlighten_pv.c
@@@ -30,8 -30,6 +30,7 @@@
#include <linux/pci.h>
#include <linux/gfp.h>
#include <linux/edd.h>
- #include <linux/objtool.h>
+#include <linux/reboot.h>
#include <xen/xen.h>
#include <xen/events.h>
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists