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=-10.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_RED,USER_AGENT_SANE_1 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 07465C48BE5 for ; Mon, 21 Jun 2021 09:00:53 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 9D9DB61002 for ; Mon, 21 Jun 2021 09:00:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9D9DB61002 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1A2FE6B00A2; Mon, 21 Jun 2021 05:00:52 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1532A6B00A3; Mon, 21 Jun 2021 05:00:52 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id F0E546B00A4; Mon, 21 Jun 2021 05:00:51 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0157.hostedemail.com [216.40.44.157]) by kanga.kvack.org (Postfix) with ESMTP id C0EF16B00A2 for ; Mon, 21 Jun 2021 05:00:51 -0400 (EDT) Received: from smtpin30.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 671A8180AD820 for ; Mon, 21 Jun 2021 09:00:51 +0000 (UTC) X-FDA: 78277135902.30.B75754B Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by imf23.hostedemail.com (Postfix) with ESMTP id 7B80EA006BF1 for ; Mon, 21 Jun 2021 09:00:48 +0000 (UTC) IronPort-SDR: E2+IGM/eIDXeI3MMb6xvqQFyZxWp8fsJI+a6v9EqOKMHCT3V11MOrM19efEPXAkeXLju0cK9a1 v2aWTfrXlFDA== X-IronPort-AV: E=McAfee;i="6200,9189,10021"; a="206625634" X-IronPort-AV: E=Sophos;i="5.83,289,1616482800"; d="scan'208";a="206625634" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2021 02:00:43 -0700 IronPort-SDR: gyMM+olsqZM252LFS82b0jBC6+ltiP3O+s+mGdzVSYtRIh/IUxaOu8W4gWz1uVlRFv11COFV7p r1Alb2AJN9pA== X-IronPort-AV: E=Sophos;i="5.83,289,1616482800"; d="scan'208";a="486414892" Received: from shao2-debian.sh.intel.com (HELO [10.239.13.11]) ([10.239.13.11]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2021 02:00:40 -0700 Subject: Re: [kbuild-all] Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' To: Matthew Wilcox , kernel test robot Cc: Dmitry Osipenko , kbuild-all@lists.01.org, Linux Memory Management List , Thierry Reding , Krzysztof Kozlowski References: <202106182209.FcQENhxk-lkp@intel.com> From: Rong Chen Message-ID: <0b29ebf9-1ef8-4377-c6c7-4a2186588150@intel.com> Date: Mon, 21 Jun 2021 17:00:38 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Authentication-Results: imf23.hostedemail.com; dkim=none; spf=none (imf23.hostedemail.com: domain of rong.a.chen@intel.com has no SPF policy when checking 192.55.52.115) smtp.mailfrom=rong.a.chen@intel.com; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=intel.com (policy=none) X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 7B80EA006BF1 X-Stat-Signature: caskk9s9hpgdhath7qumbbats7rworo6 X-HE-Tag: 1624266048-183926 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000002, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 6/18/21 10:56 PM, Matthew Wilcox wrote: > 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. > Hi Matthew, We hard coded two polices: 1. If Andrew Morton involved in the commit, we will cc linux-mm 2. If the problem repo is linux-next, we will cc linux-mm to archive these reports for a summary report (some developers want to read the original report): https://lore.kernel.org/linux-mm/609ebb8a.MY4vWDkFI93n9l1s%25lkp@intel.com/ Do you want us to adjust the polices? Best Regards, Rong Chen From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============6582724083130598187==" MIME-Version: 1.0 From: Rong Chen To: kbuild-all@lists.01.org Subject: Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' Date: Mon, 21 Jun 2021 17:00:38 +0800 Message-ID: <0b29ebf9-1ef8-4377-c6c7-4a2186588150@intel.com> In-Reply-To: List-Id: --===============6582724083130598187== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 6/18/21 10:56 PM, Matthew Wilcox wrote: > 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: te= gra: 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-ne= xt.git/commit/?id=3D56ebc9b0d77e0406aba2d900c82e79204cc7dc32 >> 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=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. > Hi Matthew, We hard coded two polices: 1. If Andrew Morton involved in the commit, = we will cc linux-mm 2. If the problem repo is linux-next, we will cc linux-mm to archive = these reports for a summary report (some developers want to read the original report): https://lore.kernel.org/linux-mm/609ebb8a.MY4vWDkFI93n9l1s%25lkp(a)intel.co= m/ Do you want us to adjust the polices? Best Regards, Rong Chen --===============6582724083130598187==--