public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>,
	Ralf Baechle <ralf@linux-mips.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Huacai Chen <chenhc@lemote.com>
Subject: linux-next: manual merge of the gpio tree with the mips tree
Date: Thu, 12 May 2016 14:17:46 +1000	[thread overview]
Message-ID: <20160512141746.11db6bd3@canb.auug.org.au> (raw)

Hi Linus,

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

  arch/mips/Kconfig

between commit:

  cec47c182286 ("MIPS: Loongson: Add Loongson-3A R2 basic support")

from the mips tree and commit:

  d30a2b47d4c2 ("MIPS: do away with ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB")

from the gpio 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 ac9bfad794eb,512b5def854d..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -1354,8 -1340,7 +1352,8 @@@ config CPU_LOONGSON
  	select CPU_SUPPORTS_HUGEPAGES
  	select WEAK_ORDERING
  	select WEAK_REORDERING_BEYOND_LLSC
 +	select MIPS_PGD_C0_CONTEXT
- 	select ARCH_REQUIRE_GPIOLIB
+ 	select GPIOLIB
  	help
  		The Loongson 3 processor implements the MIPS64R2 instruction
  		set with many extensions.

             reply	other threads:[~2016-05-12  4:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12  4:17 Stephen Rothwell [this message]
2016-05-12 13:35 ` linux-next: manual merge of the gpio tree with the mips tree Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2020-01-10  4:51 Stephen Rothwell
2020-01-13  9:12 ` Paul Kocialkowski
2020-01-13 11:45   ` Stephen Rothwell
2020-01-29 22:37 ` 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=20160512141746.11db6bd3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chenhc@lemote.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.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