All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Björn Töpel" <bjorn.topel@intel.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Ivan Khoronzhuk" <ivan.khoronzhuk@linaro.org>,
	"Alexei Starovoitov" <ast@kernel.org>
Subject: linux-next: manual merge of the tip tree with the net-next tree
Date: Fri, 18 Oct 2019 13:31:39 +1100	[thread overview]
Message-ID: <20191018133139.30c88807@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2966 bytes --]

Hi all,

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

  samples/bpf/Makefile

between commit:

  1d97c6c2511f ("samples/bpf: Base target programs rules on Makefile.target")

from the net-next tree and commit:

  fce9501aec6b ("samples/bpf: fix build by setting HAVE_ATTR_TEST to zero")

from the tip 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 samples/bpf/Makefile
index 4df11ddb9c75,42b571cde177..000000000000
--- a/samples/bpf/Makefile
+++ b/samples/bpf/Makefile
@@@ -168,38 -171,21 +168,39 @@@ always += ibumad_kern.
  always += hbm_out_kern.o
  always += hbm_edt_kern.o
  
 -KBUILD_HOSTCFLAGS += -I$(objtree)/usr/include
 -KBUILD_HOSTCFLAGS += -I$(srctree)/tools/lib/bpf/
 -KBUILD_HOSTCFLAGS += -I$(srctree)/tools/testing/selftests/bpf/
 -KBUILD_HOSTCFLAGS += -I$(srctree)/tools/lib/ -I$(srctree)/tools/include
 -KBUILD_HOSTCFLAGS += -I$(srctree)/tools/perf
 -KBUILD_HOSTCFLAGS += -DHAVE_ATTR_TEST=0
 +ifeq ($(ARCH), arm)
 +# Strip all except -D__LINUX_ARM_ARCH__ option needed to handle linux
 +# headers when arm instruction set identification is requested.
 +ARM_ARCH_SELECTOR := $(filter -D__LINUX_ARM_ARCH__%, $(KBUILD_CFLAGS))
 +BPF_EXTRA_CFLAGS := $(ARM_ARCH_SELECTOR)
 +TPROGS_CFLAGS += $(ARM_ARCH_SELECTOR)
 +endif
 +
 +TPROGS_CFLAGS += -Wall -O2
 +TPROGS_CFLAGS += -Wmissing-prototypes
 +TPROGS_CFLAGS += -Wstrict-prototypes
 +
 +TPROGS_CFLAGS += -I$(objtree)/usr/include
 +TPROGS_CFLAGS += -I$(srctree)/tools/lib/bpf/
 +TPROGS_CFLAGS += -I$(srctree)/tools/testing/selftests/bpf/
 +TPROGS_CFLAGS += -I$(srctree)/tools/lib/
 +TPROGS_CFLAGS += -I$(srctree)/tools/include
 +TPROGS_CFLAGS += -I$(srctree)/tools/perf
++TPROGS_CFLAGS += -DHAVE_ATTR_TEST=0
  
 -HOSTCFLAGS_bpf_load.o += -I$(objtree)/usr/include -Wno-unused-variable
 +ifdef SYSROOT
 +TPROGS_CFLAGS += --sysroot=$(SYSROOT)
 +TPROGS_LDFLAGS := -L$(SYSROOT)/usr/lib
 +endif
 +
 +TPROGCFLAGS_bpf_load.o += -Wno-unused-variable
  
 -KBUILD_HOSTLDLIBS		+= $(LIBBPF) -lelf
 -HOSTLDLIBS_tracex4		+= -lrt
 -HOSTLDLIBS_trace_output	+= -lrt
 -HOSTLDLIBS_map_perf_test	+= -lrt
 -HOSTLDLIBS_test_overhead	+= -lrt
 -HOSTLDLIBS_xdpsock		+= -pthread
 +TPROGS_LDLIBS			+= $(LIBBPF) -lelf
 +TPROGLDLIBS_tracex4		+= -lrt
 +TPROGLDLIBS_trace_output	+= -lrt
 +TPROGLDLIBS_map_perf_test	+= -lrt
 +TPROGLDLIBS_test_overhead	+= -lrt
 +TPROGLDLIBS_xdpsock		+= -pthread
  
  # Allows pointing LLC/CLANG to a LLVM backend with bpf support, redefine on cmdline:
  #  make samples/bpf/ LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-10-18  5:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  2:31 Stephen Rothwell [this message]
2019-10-18  5:00 ` linux-next: manual merge of the tip tree with the net-next tree Alexei Starovoitov
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15  2:13 Stephen Rothwell
2022-01-10  1:12 Stephen Rothwell
2019-02-15  2:20 Stephen Rothwell
2017-11-01  7:15 Stephen Rothwell
2017-11-01  8:18 ` Peter Zijlstra
2017-11-01  8:27   ` Ingo Molnar
2017-11-01  8:55     ` Peter Zijlstra
2017-11-01  9:04       ` Ingo Molnar
2017-11-01 10:57       ` Stephen Rothwell
2017-11-01 16:27       ` Alexei Starovoitov
2017-11-05  2:12         ` Stephen Rothwell
2017-11-01  7:10 Stephen Rothwell
2017-10-30 20:55 Mark Brown
2017-11-13  6:00 ` Stephen Rothwell
2017-08-31  3:47 Stephen Rothwell
2017-09-05  0:05 ` Stephen Rothwell
2017-02-20  1:22 Stephen Rothwell
2017-02-20  9:02 ` Daniel Borkmann
2016-12-12  2:30 Stephen Rothwell
2016-12-01  3:46 Stephen Rothwell
2016-11-17  3:04 Stephen Rothwell
2015-04-07  7:11 Stephen Rothwell
2015-04-07  7:11 ` Stephen Rothwell
2015-04-07  7:32 ` Daniel Borkmann
2015-04-07 16:10 ` Alexei Starovoitov
2015-04-07  7:04 Stephen Rothwell
2015-04-07  7:04 ` Stephen Rothwell
2015-04-07 16:11 ` Alexei Starovoitov
2015-04-07  7:00 Stephen Rothwell
2015-04-07  7:00 ` Stephen Rothwell
2015-04-07  7:30 ` Daniel Borkmann
2014-07-25  4:38 Stephen Rothwell
2014-07-25  4:38 ` Stephen Rothwell
2014-05-05  4:29 Stephen Rothwell
2014-05-05  4:29 ` Stephen Rothwell
2014-01-13  3:18 Stephen Rothwell
2014-01-13  3:18 ` Stephen Rothwell
2014-01-13  3:20 ` Stephen Rothwell
2014-01-13  3:20   ` Stephen Rothwell
2014-01-14  3:02   ` Stephen Rothwell
2014-01-14  3:02     ` Stephen Rothwell
2014-01-14  4:51     ` H. Peter Anvin
2014-01-14  5:19       ` Stephen Rothwell
2014-01-14  5:19       ` David Miller
2014-01-14  5:44         ` Stephen Rothwell
2014-01-14  5:48           ` David Miller
2014-01-14  6:10             ` Stephen Rothwell
2013-11-08  4:58 Stephen Rothwell
2013-11-08  4:58 ` Stephen Rothwell
2013-04-11  4:03 Stephen Rothwell
2013-04-11  4:03 ` 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=20191018133139.30c88807@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=acme@redhat.com \
    --cc=ast@kernel.org \
    --cc=bjorn.topel@intel.com \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.