public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>,
	Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <james.hogan@imgtec.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Cowgill <James.Cowgill@imgtec.com>
Subject: linux-next: manual merge of the vfs tree with the mips tree
Date: Wed, 12 Apr 2017 09:39:01 +1000	[thread overview]
Message-ID: <20170412093901.01dded8a@canb.auug.org.au> (raw)

Hi all,

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

  arch/mips/Kconfig

between commit:

  3c81d1369703 ("MIPS: Opt into HAVE_COPY_THREAD_TLS")

from the mips tree and commit:

  28fa21828dbd ("HAVE_ARCH_HARDENED_USERCOPY is unconditional now")

from the vfs 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 52d81ca6f74e,81ce5b4b9251..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -69,8 -68,6 +69,7 @@@ config MIP
  	select HANDLE_DOMAIN_IRQ
  	select HAVE_EXIT_THREAD
  	select HAVE_REGS_AND_STACK_ACCESS_API
- 	select HAVE_ARCH_HARDENED_USERCOPY
 +	select HAVE_COPY_THREAD_TLS
  
  menu "Machine selection"
  

             reply	other threads:[~2017-04-11 23:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 23:39 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-11  1:14 linux-next: manual merge of the vfs tree with the mips tree 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=20170412093901.01dded8a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Cowgill@imgtec.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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