linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the akpm tree with the s390 tree
@ 2019-06-20  9:59 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2019-06-20  9:59 UTC (permalink / raw)
  To: Andrew Morton, Heiko Carstens, Vasily Gorbik, Christian Borntraeger
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Matteo Croce

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

Hi all,

Today's linux-next merge of the akpm tree got a conflict in:

  drivers/s390/char/sclp_async.c

between commit:

  191fa92b3448 ("s390/sclp: remove call home support")

from the s390 tree and patch:

   proc/sysctl: add shared variables for range check

from the akpm tree.

I fixed it up (I removed the file) 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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* linux-next: manual merge of the akpm tree with the s390 tree
@ 2018-10-09  6:46 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2018-10-09  6:46 UTC (permalink / raw)
  To: Andrew Morton, Martin Schwidefsky, Heiko Carstens
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Vasily Gorbik, Mike Rapoport

[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]

Hi Andrew,

Today's linux-next merge of the akpm-current tree got a conflict in:

  arch/s390/kernel/setup.c

between commit:

  b45248da1a33 ("s390: unify stack size definitions")
  ee46f78659ac ("s390: add support for virtually mapped kernel stacks")

from the s390 tree and commit:

  ab9c2b8deb1b ("memblock: remove _virt from APIs returning virtual address")

from the akpm 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/s390/kernel/setup.c
index 2a20e6ef8369,2e29456ca11e..000000000000
--- a/arch/s390/kernel/setup.c
+++ b/arch/s390/kernel/setup.c
@@@ -418,12 -357,8 +418,12 @@@ static void __init setup_lowcore(void
  	lc->last_update_timer = S390_lowcore.last_update_timer;
  	lc->last_update_clock = S390_lowcore.last_update_clock;
  
 -	restart_stack = memblock_alloc(ASYNC_SIZE, ASYNC_SIZE);
 -	restart_stack += ASYNC_SIZE;
 +	/*
 +	 * Allocate the global restart stack which is the same for
 +	 * all CPUs in cast *one* of them does a PSW restart.
 +	 */
- 	restart_stack = memblock_virt_alloc(THREAD_SIZE, THREAD_SIZE);
++	restart_stack = memblock_alloc(THREAD_SIZE, THREAD_SIZE);
 +	restart_stack += STACK_INIT_OFFSET;
  
  	/*
  	 * Set up PSW restart to call ipl.c:do_restart(). Copy the relevant

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-06-20 10:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-20  9:59 linux-next: manual merge of the akpm tree with the s390 tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2018-10-09  6:46 Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).