From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933031AbdKAHP6 (ORCPT ); Wed, 1 Nov 2017 03:15:58 -0400 Received: from ozlabs.org ([103.22.144.67]:48305 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932930AbdKAHP4 (ORCPT ); Wed, 1 Nov 2017 03:15:56 -0400 Date: Wed, 1 Nov 2017 18:15:54 +1100 From: Stephen Rothwell To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , David Miller , Networking Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Yonghong Song Subject: linux-next: manual merge of the tip tree with the net-next tree Message-ID: <20171101181554.1826e8c8@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the tip tree got a conflict in: kernel/trace/bpf_trace.c between commits: 97562633bcba ("bpf: perf event change needed for subsequent bpf helpers") and more changes ... from the net-next tree and commit: 7d9285e82db5 ("perf/bpf: Extend the perf_event_read_local() interface, a.k.a. "bpf: perf event change needed for subsequent bpf helpers"") from the tip tree. I fixed it up (I just used the version from the net-next tree) 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