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=-5.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 40F9AC433E5 for ; Mon, 13 Jul 2020 07:29:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1F03A20702 for ; Mon, 13 Jul 2020 07:29:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=cumulusnetworks.com header.i=@cumulusnetworks.com header.b="D7xh6eu+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725818AbgGMH3T (ORCPT ); Mon, 13 Jul 2020 03:29:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47592 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729027AbgGMH3R (ORCPT ); Mon, 13 Jul 2020 03:29:17 -0400 Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 07F6DC08C5DB for ; Mon, 13 Jul 2020 00:29:17 -0700 (PDT) Received: by mail-wr1-x443.google.com with SMTP id z15so14544314wrl.8 for ; Mon, 13 Jul 2020 00:29:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=4kU8N5DeedpzZY27vYaHJmaCubANM+yECKFDBgJweY4=; b=D7xh6eu++gbVif5cEAGGKdiDsW9xxIY4MmHaAwDepJv1tFzVb7Zi9vbwXIkAq6OSMC ao2hKH3BT4xs6mO1GFJTVEZ+p1It4SRAP0g9VFFPbOgQBlsZOy0TX3yRmAuQxnyUrrNK mtOZKb8/Zj1Qnf2li7fwOFjgLdjMbc1nTKtBc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4kU8N5DeedpzZY27vYaHJmaCubANM+yECKFDBgJweY4=; b=hiRIKWl4a5D5FcFd0DWWa7Gaap+98QtjwrVl7O+RmlIUerxVI3D3+KkOWg6uugOG14 p6t8MNxSjKmlrhOzhxOKxfkDpVFr9bXworUt8L6DVE0suQsDOLBdT/R5NVQtBWfU3qMQ BCU0SITk12qth/XA7lqcT8ZfAo49pPDU149pnGsJrv1f8cqwlctRakVhYksjrc0m+eUZ ujFHiFmBBrOvTMhkjcnL26fBOqB1h8k+WIULD41ylklSrLcfmG5zxRRrF4yRY8jvcCHu WOhuIPNSbkE3KDYV1feyGgwHL50PbHo8LvBSD3dyxIqHppupxPUHW/dmDUCK7q6MvLoI Zsow== X-Gm-Message-State: AOAM532Q2qzuVGkWugQkbCh1EuZum73htHrmMH/0DA9ZOhOlcgsR0CMI LSmaJXmRSoeZh2Fj90qeMnj14w== X-Google-Smtp-Source: ABdhPJyhZaYuvI1VIdHE2m9jwzvJxy3uMEncr3I2/2Fzsq4u4hxVDd97IeUGkvgBxSbMFMvVXofGqA== X-Received: by 2002:a5d:43d0:: with SMTP id v16mr82553551wrr.296.1594625355477; Mon, 13 Jul 2020 00:29:15 -0700 (PDT) Received: from [192.168.0.109] (84-238-136-197.ip.btc-net.bg. [84.238.136.197]) by smtp.gmail.com with ESMTPSA id d13sm21582030wrq.89.2020.07.13.00.29.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Jul 2020 00:29:14 -0700 (PDT) Subject: Re: linux-next: build failure after merge of the net-next tree To: Stephen Rothwell , David Miller , Networking Cc: Linux Next Mailing List , Linux Kernel Mailing List References: <20200713115412.28aac287@canb.auug.org.au> From: Nikolay Aleksandrov Message-ID: Date: Mon, 13 Jul 2020 10:29:13 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200713115412.28aac287@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 13/07/2020 04:54, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > net/bridge/br_netlink_tunnel.c: In function '__vlan_tunnel_handle_range': > net/bridge/br_netlink_tunnel.c:271:26: error: implicit declaration of function 'br_vlan_can_enter_range'; did you mean 'br_vlan_valid_range'? [-Werror=implicit-function-declaration] > 271 | if (v && curr_change && br_vlan_can_enter_range(v, *v_end)) { > | ^~~~~~~~~~~~~~~~~~~~~~~ > | br_vlan_valid_range > > Caused by commit > > 94339443686b ("net: bridge: notify on vlan tunnel changes done via the old api") > > CONFIG_BRIDGE_VLAN_FILTERING is not set for this build. > > I have reverted that commit for today. > Oops, sorry that's my bad. I mixed br_netlink_tunnel with br_vlan_tunnel, the latter is compiled only when bridge vlan filtering is defined. Anyway, I'll post a fix ASAP. Thanks.