All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Thadeu Lima de Souza Cascardo <cascardo@redhat.com>
Subject: Re: linux-next: manual merge of the powerpc tree with Linus' tree
Date: Wed, 29 Jun 2016 10:54:26 +0530	[thread overview]
Message-ID: <20160629052426.GB14508@naverao1-tp.localdomain> (raw)
In-Reply-To: <20160629103507.52c60714@canb.auug.org.au>

On 2016/06/29 10:35AM, Stephen Rothwell wrote:
> Hi all,

Hi Stephen,

> 
> Today's linux-next merge of the powerpc tree got a conflict in:
> 
>   arch/powerpc/Kconfig
> 
> between commit:
> 
>   844e3be47693 ("powerpc/bpf/jit: Disable classic BPF JIT on ppc64le")

Ah, I see that the above commit is not part of powerpc next tree, which 
explains the conflict.

> 
> from Linus' tree and commit:
> 
>   156d0e290e96 ("powerpc/ebpf/jit: Implement JIT compiler for extended BPF")
> 
> from the powerpc tree.
> 
> I fixed it up (see below - I am not sure this entirely correct) 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/powerpc/Kconfig
> index 0a9d439bcda6,ee82f9a09a85..000000000000
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@@ -128,7 -128,8 +128,8 @@@ config PP
>   	select IRQ_FORCED_THREADING
>   	select HAVE_RCU_TABLE_FREE if SMP
>   	select HAVE_SYSCALL_TRACEPOINTS
> - 	select HAVE_CBPF_JIT if CPU_BIG_ENDIAN
>  -	select HAVE_CBPF_JIT if !PPC64
> ++	select HAVE_CBPF_JIT if !PPC64 && CPU_BIG_ENDIAN

'if !PPC64' condition is sufficient, though having the BIG_ENDIAN check 
should be ok too.

Thanks,
Naveen

> + 	select HAVE_EBPF_JIT if PPC64
>   	select HAVE_ARCH_JUMP_LABEL
>   	select ARCH_HAVE_NMI_SAFE_CMPXCHG
>   	select ARCH_HAS_GCOV_PROFILE_ALL
> 

  reply	other threads:[~2016-06-29  5:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  0:35 linux-next: manual merge of the powerpc tree with Linus' tree Stephen Rothwell
2016-06-29  0:35 ` Stephen Rothwell
2016-06-29  5:24 ` Naveen N. Rao [this message]
2016-06-29  6:33   ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2021-08-15 22:27 Stephen Rothwell
2021-08-15 22:27 ` Stephen Rothwell
2018-08-14 23:19 Stephen Rothwell
2017-11-07 22:32 Stephen Rothwell
2017-10-30 12:51 Mark Brown
2017-11-13  5:37 ` Stephen Rothwell
2017-02-16 22:06 Stephen Rothwell
2016-05-01 23:50 Stephen Rothwell
2016-05-01 23:50 ` Stephen Rothwell
2014-05-29  2:04 Stephen Rothwell
2014-05-29  2:04 ` Stephen Rothwell
2009-12-08 23:49 Stephen Rothwell
2009-12-08 23:49 ` 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=20160629052426.GB14508@naverao1-tp.localdomain \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=cascardo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.