linux-next: manual merge of the akpm-current tree with the tip tree

From: Stephen Rothwell
Date: Mon Jun 24 2019 - 06:25:05 EST

Hi all,

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


between commit:

d5f34153e526 ("debugobjects: Move printk out of db->lock critical sections")

from the tip tree and commit:

8b6b497dfb11 ("lib/debugobjects.c: move printk out of db lock critical sections")

from the akpm-current tree.

I fixed it up (I reverted the akpm-current tree version) 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.

Stephen Rothwell

Attachment: pgpS0YoJrNYO6.pgp
Description: OpenPGP digital signature