From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DFE5AC433E1 for ; Tue, 14 Jul 2020 06:17:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B595E221E8 for ; Tue, 14 Jul 2020 06:17:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="DG6SCwRh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725853AbgGNGRG (ORCPT ); Tue, 14 Jul 2020 02:17:06 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:46575 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725788AbgGNGRG (ORCPT ); Tue, 14 Jul 2020 02:17:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1594707424; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5237IuvMgTeLcciR2WRdBusDhcq3/u6O0nS/R7VQZtk=; b=DG6SCwRhWSBe/Bt7cFTfl8mYiLyJeDGqpgc569GwwszZB15dUhTbP+ziZNrNsxYJWJmAbz 1nkx2DDmMX9P3f8pIdUFL8nQmpXJdy1eOHpvayhQdIy0t/8bq8Ysk6jTAglkcmnI1Asz+e QTXHND5zZBKWApbqdMEKgmtLG9Ij+hQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-60-8l_nubbtMx6PjXy50fqnoA-1; Tue, 14 Jul 2020 02:16:59 -0400 X-MC-Unique: 8l_nubbtMx6PjXy50fqnoA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 76D2F184C5E1; Tue, 14 Jul 2020 06:16:57 +0000 (UTC) Received: from krava (unknown [10.40.193.14]) by smtp.corp.redhat.com (Postfix) with SMTP id 69B0272E4D; Tue, 14 Jul 2020 06:16:55 +0000 (UTC) Date: Tue, 14 Jul 2020 08:16:54 +0200 From: Jiri Olsa To: Stephen Rothwell Cc: Daniel Borkmann , Alexei Starovoitov , Networking , Linux Next Mailing List , Linux Kernel Mailing List , Jiri Olsa Subject: Re: linux-next: build failure after merge of the bpf-next tree Message-ID: <20200714061654.GE183694@krava> References: <20200714122247.797cf01e@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200714122247.797cf01e@canb.auug.org.au> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the bpf-next tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > tmp/ccsqpVCY.s: Assembler messages: > tmp/ccsqpVCY.s:78: Error: unrecognized symbol type "" > tmp/ccsqpVCY.s:91: Error: unrecognized symbol type "" > > I don't know what has caused this (I guess maybe the resolve_btfids > branch). > > I have used the bpf-next tree from next-20200713 for today. ok, trying to reproduce thanks, jirka