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=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 C9665C48BDF for ; Fri, 18 Jun 2021 14:57:13 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6FBF3613B4 for ; Fri, 18 Jun 2021 14:57:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6FBF3613B4 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 0E7AB6B0075; Fri, 18 Jun 2021 10:57:13 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 097576B007B; Fri, 18 Jun 2021 10:57:13 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EA18F6B007D; Fri, 18 Jun 2021 10:57:12 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0104.hostedemail.com [216.40.44.104]) by kanga.kvack.org (Postfix) with ESMTP id B8D036B0075 for ; Fri, 18 Jun 2021 10:57:12 -0400 (EDT) Received: from smtpin17.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 586C58249980 for ; Fri, 18 Jun 2021 14:57:12 +0000 (UTC) X-FDA: 78267147504.17.852314B Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf11.hostedemail.com (Postfix) with ESMTP id B8358200110F for ; Fri, 18 Jun 2021 14:57:11 +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=0MbpSSOBpXHmidottzKsqEs5ZvnKhtABbeXsCXzMRe0=; b=YtQ60Ky1hL4HkxnB5qN7/0qeWW 5nWPPhySTEvdi8wcpsPlWgcDhwR1FkA9QyncekFpM/yLM3XhZNItB3xyuGii8ncb72e5pQVdBkBbt rVuzpaYI2MtWtjGag4/+RhIwNAAu3qtNSat+Aku8pICTX6w3qyq8YjBow+BVUfy6DM5ABajt77o9W 0UApSPddl4Q1LvHKgUE3U1+rKyBsrY9nuRTkGzG8aCbW1U039l/oTBrglCog5YUo0Au7TDxAzb4bO +HcX7OCdM8nLC/MVfBEzNUHJjlhDFTfL3mLhZXXmdIZZhNFsLMcACSnzTwELKfL4zH0wSORMt2g0D Wqv9wpkA==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1luFv2-00ANke-FP; Fri, 18 Jun 2021 14:56:40 +0000 Date: Fri, 18 Jun 2021 15:56:28 +0100 From: Matthew Wilcox To: kernel test robot Cc: Dmitry Osipenko , kbuild-all@lists.01.org, Linux Memory Management List , Thierry Reding , Krzysztof Kozlowski Subject: Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' Message-ID: References: <202106182209.FcQENhxk-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202106182209.FcQENhxk-lkp@intel.com> Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=YtQ60Ky1; spf=none (imf11.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none X-Stat-Signature: rh7abuxrg3kxuqtm9xy96pjcwdo8us85 X-Rspamd-Queue-Id: B8358200110F X-Rspamd-Server: rspam06 X-HE-Tag: 1624028231-885398 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 10:42:13PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: e71e3a48a7e89fa71fb70bf4602367528864d2ff > commit: 56ebc9b0d77e0406aba2d900c82e79204cc7dc32 [5946/11253] memory: tegra: Enable compile testing for all drivers > config: x86_64-randconfig-c002-20210618 (attached as .config) > compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 > reproduce (this is a W=1 build): > # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=56ebc9b0d77e0406aba2d900c82e79204cc7dc32 > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > git fetch --no-tags linux-next master > git checkout 56ebc9b0d77e0406aba2d900c82e79204cc7dc32 > # save the attached .config to linux build tree > make W=1 ARCH=x86_64 What is it about this failure that makes the lkp bot think that linux-mm is an appropriate cc? It seems to get cc'd on all kinds of random bugs, and I'm never quite sure why. From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8878549114036667848==" MIME-Version: 1.0 From: Matthew Wilcox To: kbuild-all@lists.01.org Subject: Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' Date: Fri, 18 Jun 2021 15:56:28 +0100 Message-ID: In-Reply-To: <202106182209.FcQENhxk-lkp@intel.com> List-Id: --===============8878549114036667848== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Fri, Jun 18, 2021 at 10:42:13PM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.g= it master > head: e71e3a48a7e89fa71fb70bf4602367528864d2ff > commit: 56ebc9b0d77e0406aba2d900c82e79204cc7dc32 [5946/11253] memory: teg= ra: Enable compile testing for all drivers > config: x86_64-randconfig-c002-20210618 (attached as .config) > compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 > reproduce (this is a W=3D1 build): > # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next= .git/commit/?id=3D56ebc9b0d77e0406aba2d900c82e79204cc7dc32 > git remote add linux-next https://git.kernel.org/pub/scm/linux/ke= rnel/git/next/linux-next.git > git fetch --no-tags linux-next master > git checkout 56ebc9b0d77e0406aba2d900c82e79204cc7dc32 > # save the attached .config to linux build tree > make W=3D1 ARCH=3Dx86_64 = What is it about this failure that makes the lkp bot think that linux-mm is an appropriate cc? It seems to get cc'd on all kinds of random bugs, and I'm never quite sure why. --===============8878549114036667848==--