From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Atish Patra <atish.patra@wdc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>
Subject: linux-next: manual merge of the risc-v tree with the arm64 tree
Date: Thu, 28 Jan 2021 10:27:47 +1100 [thread overview]
Message-ID: <20210128102747.3ae8e5eb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Hi all,
Today's linux-next merge of the risc-v tree got a conflict in:
arch/arm64/mm/Makefile
between commit:
072e3d96a79a ("arm64: hibernate: move page handling function to new trans_pgd.c")
from the arm64 tree and commit:
ae3c107cd8be ("numa: Move numa implementation to common code")
from the risc-v 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/arm64/mm/Makefile
index 77222d92667a,cd60e4fed78f..000000000000
--- a/arch/arm64/mm/Makefile
+++ b/arch/arm64/mm/Makefile
@@@ -6,8 -6,6 +6,7 @@@ obj-y := dma-mapping.o extable.o fau
obj-$(CONFIG_HUGETLB_PAGE) += hugetlbpage.o
obj-$(CONFIG_PTDUMP_CORE) += ptdump.o
obj-$(CONFIG_PTDUMP_DEBUGFS) += ptdump_debugfs.o
+obj-$(CONFIG_TRANS_TABLE) += trans_pgd.o
- obj-$(CONFIG_NUMA) += numa.o
obj-$(CONFIG_DEBUG_VIRTUAL) += physaddr.o
obj-$(CONFIG_ARM64_MTE) += mteswap.o
KASAN_SANITIZE_physaddr.o += n
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-01-27 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 23:27 Stephen Rothwell [this message]
2021-02-14 21:52 ` linux-next: manual merge of the risc-v tree with the arm64 tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-03-14 23:31 Stephen Rothwell
2024-03-15 17:21 ` Palmer Dabbelt
2024-03-15 18:19 ` Catalin Marinas
2019-08-12 23:34 Stephen Rothwell
2019-08-13 8:24 ` Will Deacon
2019-08-13 8:42 ` Stephen Rothwell
2019-08-13 8:53 ` Will Deacon
2019-08-13 22:24 ` Paul Walmsley
2019-08-14 9:00 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210128102747.3ae8e5eb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=pasha.tatashin@soleen.com \
--cc=paul@pwsan.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox