Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 10 Dec 2020 15:58:08 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Michal Simek <monstr@monstr.eu>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the tip tree with the microblaze tree
Message-ID: <20201210155808.717a7257@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/0Px9Bv/_pfqEcRM/0cBgiQx";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/0Px9Bv/_pfqEcRM/0cBgiQx
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

Today's linux-next merge of the tip tree got conflicts in:

  arch/microblaze/Kconfig
  arch/microblaze/mm/Makefile

between commit:

  05cdf457477d ("microblaze: Remove noMMU code")

from the microblaze tree and commit:

  7ac1b26b0a72 ("microblaze/mm/highmem: Switch to generic kmap atomic")

from the 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.

--=20
Cheers,
Stephen Rothwell

diff --cc arch/microblaze/Kconfig
index 6acbb4571b0f,7f6ca0ab4f81..000000000000
--- a/arch/microblaze/Kconfig
+++ b/arch/microblaze/Kconfig
@@@ -139,8 -143,19 +139,9 @@@ config ADVANCED_OPTION
  comment "Default settings for advanced configuration options are used"
  	depends on !ADVANCED_OPTIONS
 =20
 -config XILINX_UNCACHED_SHADOW
 -	bool "Are you using uncached shadow for RAM ?"
 -	depends on ADVANCED_OPTIONS && !MMU
 -	default n
 -	help
 -	  This is needed to be able to allocate uncachable memory regions.
 -	  The feature requires the design to define the RAM memory controller
 -	  window to be twice as large as the actual physical memory.
 -
  config HIGHMEM
  	bool "High memory support"
 -	depends on MMU
+ 	select KMAP_LOCAL
  	help
  	  The address space of Microblaze processors is only 4 Gigabytes large
  	  and it has to accommodate user address space, kernel address
diff --cc arch/microblaze/mm/Makefile
index cd8a844bf29e,8ced71100047..000000000000
--- a/arch/microblaze/mm/Makefile
+++ b/arch/microblaze/mm/Makefile
@@@ -5,5 -5,4 +5,4 @@@
 =20
  obj-y :=3D consistent.o init.o
 =20
 -obj-$(CONFIG_MMU) +=3D pgtable.o mmu_context.o fault.o
 +obj-y +=3D pgtable.o mmu_context.o fault.o
- obj-$(CONFIG_HIGHMEM) +=3D highmem.o

--Sig_/0Px9Bv/_pfqEcRM/0cBgiQx
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl/RquEACgkQAVBC80lX
0GwGKQgAknIQ1cKhiwukVfmkyHholoPB+hmqbxERg2Sa7XnmRmzZ9YE/x7y+hSON
LpJbj3+JqJP4Uwr61OsRz+dyjszzbynJlIE8zp9Wn3lxVGvebPEHkLkheuyUzN45
p3mScVTDz6FGoVJcX7v1JMFLwiv2j0IQFIb2ej6x5Bja3RJMClpKB5XY2tMZtnXU
PzM4qVrM1CI57NR8VPiiNPzsA8F4wKrSHyH19w/Ao/gRSvKoBDrZSnxI5zuk+f8J
6Utja/vnPNjtF6kLCI6mtjfEePFgFse7NKOyJvXDO9UA2MgbByJsaN2yBQuETm5N
IEYXE8YfXR5JDphR0d5GM8pojsKfoA==
=NHPY
-----END PGP SIGNATURE-----

--Sig_/0Px9Bv/_pfqEcRM/0cBgiQx--