Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp308579imm; Thu, 2 Aug 2018 19:45:34 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcvfRaE50LETYaSXt/KlD7iKUcJeryPKsayyIHIQujfKUMR7qjUEzP8rrGFGpDy39lwf12o X-Received: by 2002:a17:902:7845:: with SMTP id e5-v6mr1720510pln.197.1533264334247; Thu, 02 Aug 2018 19:45:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533264334; cv=none; d=google.com; s=arc-20160816; b=NkcV6NSRvZTRXUwA0yXzbPcPsB2R0d6EhMAP3rBuC4Z+Dud/8XoX61bRZtOF1fBdfI a40zSpD0cfr6D776IBBOTGuupK4/0AQWiZQyZ043tduhf189+51ry2Ivuwx5ANOsuA0B rY7W82Dof63fdananJZ5trp9L0vBe0HunvV8mRBZxiws7HKAXfXiqGUaldWevtl8KDGv zk0NQh55NoJ0CUHTTgQUBbuttkaTXHHNVcOhoDY8V1SJ6ra/Wzn7vhiB28jWL89W5oZt H6bvDEC5N4dDlHdxpP337y30pL1rcNAh7jSAZMcwQLPxo49WtOlNxyrBOMdtFjbIaZIC +ojA== 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:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=NvFLMnQfSX7T90se1V7zRuBSp+5goIMFVd3b/9396BQ=; b=AC9T+/o7FzmrDPDivy6wHwlQo9NLu7b9pUh2Ge94bSl09RdXKCUQozn7bcqxbGQVRD 0AGYZTqmzefBgo0wlxmut005bfpGZZkw2EqLDGi4f4cnXXYHi3AuCt28x97y4TX3q48O U+8Wi2PwD4ioPe15h29dhxodWlkFmIKQmI8J0kuaNg8OXUFMfrecZGyq7zjKBI4EB8Ac VTA3RbAgzAp/03XUFOli09eiR/kLUsVPRfTBb5EUysNt+SIcIZch3KHsjjY9nvRSkExy ICv+Dfsr6NXHhFfK5VfQ5DvwlcThu4u0sWyIavGsbiV1ZRdkybOwQ/2KIVhjXERtj+Ko f7qQ== 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 t196-v6si3247326pgc.308.2018.08.02.19.45.19; Thu, 02 Aug 2018 19:45:34 -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 S1727257AbeHCEid (ORCPT + 99 others); Fri, 3 Aug 2018 00:38:33 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:51586 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726190AbeHCEid (ORCPT ); Fri, 3 Aug 2018 00:38:33 -0400 Received: from localhost (unknown [172.58.41.75]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 4A2FE13EBDE9F; Thu, 2 Aug 2018 19:44:30 -0700 (PDT) Date: Thu, 02 Aug 2018 19:44:26 -0700 (PDT) Message-Id: <20180802.194426.2272443689594696355.davem@davemloft.net> To: sfr@canb.auug.org.au Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the net-next tree From: David Miller In-Reply-To: <20180803121430.25899c83@canb.auug.org.au> References: <20180803121430.25899c83@canb.auug.org.au> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 02 Aug 2018 19:44:30 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Stephen Rothwell Date: Fri, 3 Aug 2018 12:14:30 +1000 > Hi all, > > After merging the net-next tree, today's linux-next build (perf) failed > like this: > > In file included from btf.c:10:0: ... > Caused by commit > > 89b1698c93a9 ("Merge ra.kernel.org:/pub/scm/linux/kernel/git/davem/net") > > Some of the lines in tools/lib/bpf/btf.[ch] were duplicated (they existed > on both sides of the merge). > > I have used the net-next tree from next-20180802 for today. My bad, I am working on fixing this now. Thanks.