Received: by 10.192.165.148 with SMTP id m20csp1720375imm; Thu, 26 Apr 2018 00:57:58 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/AmuSohVS33ZhyJXG3FgAk/zwgVIEte6Dy5saZ+11HZkrQ+kZTjy1GwatH+cZBu7Wt7nt6 X-Received: by 2002:a17:902:1744:: with SMTP id i62-v6mr28731165pli.267.1524729478467; Thu, 26 Apr 2018 00:57:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524729478; cv=none; d=google.com; s=arc-20160816; b=LTJUIOiAwdMiHzdwzqxKnDjp7/2o0jN8C0gTtXRa+V/BbxhXBzA7ei7CErm2lOBRHK bi3GskHOe2TzlvgMIaezJw3c50Kxaen1+9Lik/JlzglS1W+plI8khCWuyv2xTucGJ9nK R0mI4dVW4TX5BZ8jU8nUz2Yk7cKs0I9cGdWegn9WbT5KjlAy8k0dOePimwQ3mPHYJrSz ppGYPRDaY85sN8QvP0jv5ELqFCJZutKTR7hWmRD4vewbRXPx9KyHvbrowPh9ou0xCOZU G44h0Xyfq56kIVRtEbU+2zlXS5LdRUFPCVeQBauSXHppCTbxPrQofO/LmwAr6G4HgpJi e2nQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=0ctmHBfjQQbr1vxOQWnXeK1BCfygwMOqo0QD3ixpvHk=; b=zzV2yhOVUG5IN2U5hdUToRjlBQzSQs2hQzG3vCXpBMCZV2KlF/omyLUqmRXb7RTcoE bmJr/SLJTcJDoCRdnRFvFZrbPhHcX9CB2H0lccBp/yPpL7BXFd2TynFaTYBLzYvDQ983 Wz1SP+t8o38zSMTk9d8jOpiiNWEkVbwBvoDiZ61fDIUFXxHPTpNjLso1nwpklZhegAmt gUrg3+QXC1H9eHT/Ge+tm8zWsyJEe86Lbfykh4rzScvgxvsgRK3PzoIiNnw2+mFF8i6u makogQtYR4AfiZP/NUAeLzlXTSncOYHXuvyxQGhDMCwyulJ0RoDK6CR+05T9/HonIDPX vGRw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y190si18380204pfy.75.2018.04.26.00.57.44; Thu, 26 Apr 2018 00:57:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754234AbeDZH42 (ORCPT + 99 others); Thu, 26 Apr 2018 03:56:28 -0400 Received: from www62.your-server.de ([213.133.104.62]:49514 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753000AbeDZH41 (ORCPT ); Thu, 26 Apr 2018 03:56:27 -0400 Received: from [188.63.75.139] (helo=linux.home) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85_2) (envelope-from ) id 1fBblN-000271-Vw; Thu, 26 Apr 2018 09:56:22 +0200 Subject: Re: linux-next: manual merge of the bpf-next tree with the net-next tree To: Stephen Rothwell , Alexei Starovoitov , Networking , David Miller Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Anders Roxell References: <20180426104902.548c3fdb@canb.auug.org.au> From: Daniel Borkmann Message-ID: <946a88a7-a12b-ab57-9f6a-17cf4f9aecfb@iogearbox.net> Date: Thu, 26 Apr 2018 09:56:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20180426104902.548c3fdb@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.99.3/24514/Thu Apr 26 06:27:07 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/26/2018 02:49 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the bpf-next tree got a conflict in: > > tools/testing/selftests/bpf/.gitignore > > between commit: > > 0abf854d7cbb ("selftests: bpf: update .gitignore with missing generated files") > > from the net-next tree and commit: > > b6fd9cf796e6 ("selftests: bpf: update .gitignore with missing file") > > from the bpf-next 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. Looks good, thanks!