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=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,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 CFE88C48BE8 for ; Fri, 18 Jun 2021 15:01:35 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 7BFA761260 for ; Fri, 18 Jun 2021 15:01:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7BFA761260 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 12FED6B0075; Fri, 18 Jun 2021 11:01:35 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0E05B6B007B; Fri, 18 Jun 2021 11:01:35 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EEA426B007D; Fri, 18 Jun 2021 11:01:34 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0058.hostedemail.com [216.40.44.58]) by kanga.kvack.org (Postfix) with ESMTP id BDD2B6B0075 for ; Fri, 18 Jun 2021 11:01:34 -0400 (EDT) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 56B46180AD838 for ; Fri, 18 Jun 2021 15:01:34 +0000 (UTC) X-FDA: 78267158508.23.85E8720 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf29.hostedemail.com (Postfix) with ESMTP id E43D0577 for ; Fri, 18 Jun 2021 15:01:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=lE6/LRNU2ACZUrRFcA6pvNzr0RrB0aVnorgMrzorXY8=; b=iGLZeQ07H//y78XX+fzrFvcSUW JJO1UBkvT2AkobcDU/hN847hRjnuGxYWsV5C3TA56sgLX04l0qPA9XvSOM8/5CTv4uKWdhhhWxEE2 PSTQDVL8RCbwKRms9xDkyoFM6JRxw2R947z/BDHwrhGT8n2E37d1FqCySAgxA9XJQxhnCSXlzEGB/ dDcagxEtB/YiLlcRNyh0sQZcT8s0Z40Chl62cPYaIHiY45fKRmSITY4Mj3TWaYvfl5mjyfTIR6Spm N/Bd2EI7wl/5acNQIUCG7CGTaj4i5C4b4cAIk0DG7QZmdamfoCyozD+KONZ4k0EPGcHQDouNhY4aI gy58StIg==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1luFyw-00AO1i-3k; Fri, 18 Jun 2021 15:00:42 +0000 Date: Fri, 18 Jun 2021 16:00:30 +0100 From: Matthew Wilcox To: Krzysztof Kozlowski Cc: Thierry Reding , kernel test robot , Philipp Zabel , Dmitry Osipenko , "kbuild-all@lists.01.org" , "clang-built-linux@googlegroups.com" , Linux Memory Management List Subject: Re: [linux-next:master 5946/11253] ld.lld: error: undefined symbol: reset_controller_register Message-ID: References: <202106182243.KgZxMD9A-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=iGLZeQ07; dmarc=none; spf=none (imf29.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org X-Stat-Signature: fu7abhj1chg49it8nr33jjrm7rwmwmau X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: E43D0577 X-HE-Tag: 1624028492-819634 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Jun 18, 2021 at 04:55:23PM +0200, Krzysztof Kozlowski wrote: > These are randconfigs, so I don't think Linus will hit them when > merging. Therefore assuming the reset-stubs are applied (and tree is in > next), we should be fine, shouldn't we? It's a bisection hazard. Please fix it before the merge. This is exactly the kind of thing that linux-next is designed to detect.