From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <james.hogan@imgtec.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Maksym Kokhan <maksym.kokhan@globallogic.com>,
Paul Burton <paul.burton@mips.com>,
Andrii Bordunov <andrew.bordunov@gmail.com>
Subject: linux-next: manual merge of the mips tree with the kbuild tree
Date: Mon, 26 Nov 2018 10:17:12 +1100 [thread overview]
Message-ID: <20181126101712.18480f3c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/Kconfig
between commit:
eb01d42a7778 ("PCI: consolidate PCI config entry in drivers/pci")
from the kbuild tree and commit:
47bf2b031754 ("mips: sort list of configs for Malta")
from the mips 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/mips/Kconfig
index f4df8007fddb,e49b5a0c8585..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -495,22 -498,23 +499,23 @@@ config MIPS_MALT
select BOOT_RAW
select BUILTIN_DTB
select CEVT_R4K
- select CSRC_R4K
select CLKSRC_MIPS_GIC
select COMMON_CLK
+ select CSRC_R4K
select DMA_MAYBE_COHERENT
select GENERIC_ISA_DMA
- select HAVE_PCSPKR_PLATFORM
- select IRQ_MIPS_CPU
- select MIPS_GIC
+ select HAVE_PCI
+ select HAVE_PCSPKR_PLATFORM
- select HW_HAS_PCI
select I8253
select I8259
+ select IRQ_MIPS_CPU
+ select LIBFDT
select MIPS_BONITO64
select MIPS_CPU_SCACHE
+ select MIPS_GIC
select MIPS_L1_CACHE_SHIFT_6
- select PCI_GT64XXX_PCI0
select MIPS_MSC
+ select PCI_GT64XXX_PCI0
select SMP_UP if SMP
select SWAP_IO_SPACE
select SYS_HAS_CPU_MIPS32_R1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-11-25 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 23:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-25 23:17 linux-next: manual merge of the mips tree with the kbuild tree Stephen Rothwell
2018-08-02 23:21 Stephen Rothwell
2018-08-03 6:41 ` Christoph Hellwig
2018-08-03 6:42 ` Stephen Rothwell
2018-08-03 7:12 ` Christoph Hellwig
2018-08-03 7:51 ` Stephen Rothwell
2018-08-14 23:31 ` Stephen Rothwell
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=20181126101712.18480f3c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrew.bordunov@gmail.com \
--cc=hch@lst.de \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maksym.kokhan@globallogic.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).