Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp108681pxu; Tue, 6 Oct 2020 01:55:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz1IJpqOUpVJJyItCsM7wFeOARc3YVZ1FacRJ+laszk4PbQ2AE1moVniwohGpK98RsFuqpu X-Received: by 2002:a50:a452:: with SMTP id v18mr4129633edb.143.1601974507101; Tue, 06 Oct 2020 01:55:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601974507; cv=none; d=google.com; s=arc-20160816; b=vM7XSy0nK/cBn8Isyms4vsk4FE0rO39RKwmSAMmVwmm47I0ptGtRm+Di1UsrBtXq2T bx7WCFKBHxNexjNc2ChlEw0+gKnIAwEjUyUfdd+Qpu6iRiojib2Nl4m5w6JAoD/tCCa4 G6dTD7S5XlXnyrCt/Ge8quOoniyt2Yq/lVwjSWBE/wsaiC1fNaxUWOpZ4FKbJ2qQYQiP y+wQ6Gh+fzP2TX1TGyQSBqfG4pEr3/7Z8gvmPIm/zAYUab6QpZw965FTOxNQ3CLzENdE MqL7kobzgBAHCQo7Z7qkEeHR1p79MwkNIfFUmWL6MaZ7Do4sZNTSbbsq/GodR+pk+OlS h8nQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=N7VW7yaL3Zmpa8Nl7DIGLw+7kJHqWdXdXQ1WcIO6m/A=; b=fo324go3G7ofaKqYzLOoulywi8Zh4cjmMUcTm64hJdzchSAWm3oZIHMBMT6WEJRSJp GpwxlHFd0FM/Anctx3fzG1yM0Ir6qFGeMYphyBZcz9xQHnZDO9vBz8v4IWAliWnHRjkT 0Cs6jgwX8Xa7YVHGiDD3YvxnE7aNgZxj3qJ4m4Pb/aFSIAomUImue3SJJP9MuF3RQnGq z0ezC12pUID8HNYReYi73pCg7pf28hEFR+0McbjEC7v6xnxIPJ2sQTRtQ5gSx2Nl1Hfr REW/K/2Lch/CBDYENcsGUsqJLdqYIq5wwSuHUm/uvVQ8n2CI8lmlCSnSLSjeWe68XWaI mNlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p17si193210edx.292.2020.10.06.01.54.43; Tue, 06 Oct 2020 01:55:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726105AbgJFIxl (ORCPT + 99 others); Tue, 6 Oct 2020 04:53:41 -0400 Received: from www62.your-server.de ([213.133.104.62]:57228 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbgJFIxk (ORCPT ); Tue, 6 Oct 2020 04:53:40 -0400 Received: from sslproxy06.your-server.de ([78.46.172.3]) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1kPiiu-0008NA-2X; Tue, 06 Oct 2020 10:53:28 +0200 Received: from [178.196.57.75] (helo=pc-9.home) by sslproxy06.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPiit-0000Io-S3; Tue, 06 Oct 2020 10:53:27 +0200 Subject: Re: linux-next: build failure after merge of the net-next tree To: Stephen Rothwell , Christoph Hellwig Cc: David Miller , Networking , Linux Kernel Mailing List , Linux Next Mailing List , Magnus Karlsson References: <20201006145847.14093e47@canb.auug.org.au> <20201006051301.GA5917@lst.de> <20201006164124.1dfa2543@canb.auug.org.au> From: Daniel Borkmann Message-ID: <173e6f80-2211-a614-2953-0f3df35491a9@iogearbox.net> Date: Tue, 6 Oct 2020 10:53:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20201006164124.1dfa2543@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.102.4/25948/Mon Oct 5 16:02:22 2020) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/6/20 7:41 AM, Stephen Rothwell wrote: > On Tue, 6 Oct 2020 07:13:01 +0200 Christoph Hellwig wrote: >> >> On Tue, Oct 06, 2020 at 02:58:47PM +1100, Stephen Rothwell wrote: >>> Hi all, >>> >>> After merging the net-next tree, today's linux-next build (x86_64 >>> allmodconfig) failed like this: >> >> It actually doesn't need that or the two other internal headers. >> Bjoern has a fixed, and it was supposed to be queued up according to >> patchwork. > > Yeah, it is in the bpf-next tree but not merged into the net-next tree > yet. Yep, applied yesterday. Given a3cf77774abf ("dma-mapping: merge into ") is in dma-mapping tree and not yet affecting bpf-next nor net-next, we were planning to ship bpf-next at the usual cadence this week, so it'll be in net-next end of week for sure. (If there is urgent reason to have it in net-next today, please let us know of course.) Thanks, Daniel