Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1390659 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-04-29 02:10 +0200 |
| Last post | 2016-04-29 10:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
linux-next: manual merge of the arm64 tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-29 02:10 +0200
Re: linux-next: manual merge of the arm64 tree with Linus' tree Will Deacon <will.deacon@arm.com> - 2016-04-29 10:50 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-04-29 02:10 +0200 |
| Subject | linux-next: manual merge of the arm64 tree with Linus' tree |
| Message-ID | <rt4am-4LZ-25@gated-at.bofh.it> |
Hi Catalin,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm/kvm/arm.c
between commit:
06a71a24bae5 ("arm64: KVM: unregister notifiers in hyp mode teardown path")
from Linus' tree and commit:
67f691976662 ("arm64: kvm: allows kvm cpu hotplug")
from the arm64 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/arm/kvm/arm.c
index dded1b763c16,1687e1450c3a..000000000000
--- a/arch/arm/kvm/arm.c
+++ b/arch/arm/kvm/arm.c
@@@ -1198,8 -1226,6 +1233,7 @@@ static void teardown_hyp_mode(void
free_hyp_pgds();
for_each_possible_cpu(cpu)
free_page(per_cpu(kvm_arm_hyp_stack_page, cpu));
- unregister_cpu_notifier(&hyp_init_cpu_nb);
+ hyp_cpu_pm_exit();
}
static int init_vhe_mode(void)
[toc] | [next] | [standalone]
| From | Will Deacon <will.deacon@arm.com> |
|---|---|
| Date | 2016-04-29 10:50 +0200 |
| Message-ID | <rtchA-2Tn-27@gated-at.bofh.it> |
| In reply to | #1390659 |
On Fri, Apr 29, 2016 at 09:59:58AM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the arm64 tree got a conflict in:
>
> arch/arm/kvm/arm.c
>
> between commit:
>
> 06a71a24bae5 ("arm64: KVM: unregister notifiers in hyp mode teardown path")
>
> from Linus' tree and commit:
>
> 67f691976662 ("arm64: kvm: allows kvm cpu hotplug")
>
> from the arm64 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/arm/kvm/arm.c
> index dded1b763c16,1687e1450c3a..000000000000
> --- a/arch/arm/kvm/arm.c
> +++ b/arch/arm/kvm/arm.c
> @@@ -1198,8 -1226,6 +1233,7 @@@ static void teardown_hyp_mode(void
> free_hyp_pgds();
> for_each_possible_cpu(cpu)
> free_page(per_cpu(kvm_arm_hyp_stack_page, cpu));
> - unregister_cpu_notifier(&hyp_init_cpu_nb);
> + hyp_cpu_pm_exit();
> }
>
> static int init_vhe_mode(void)
Thanks Stephen, this looks good to me.
Will
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web