From: Rong Chen <rong.a.chen@intel.com>
To: Matthew Wilcox <willy@infradead.org>, kernel test robot <lkp@intel.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Thierry Reding <treding@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register'
Date: Mon, 21 Jun 2021 17:00:38 +0800 [thread overview]
Message-ID: <0b29ebf9-1ef8-4377-c6c7-4a2186588150@intel.com> (raw)
In-Reply-To: <YMy0HKDOMmIRew5b@casper.infradead.org>
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 <akpm@linux-foundation.org> 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
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
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 [thread overview]
Message-ID: <0b29ebf9-1ef8-4377-c6c7-4a2186588150@intel.com> (raw)
In-Reply-To: <YMy0HKDOMmIRew5b@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
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 <akpm@linux-foundation.org> 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.com/
Do you want us to adjust the polices?
Best Regards,
Rong Chen
next prev parent reply other threads:[~2021-06-21 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 14:42 [linux-next:master 5946/11253] mc.c:undefined reference to `reset_controller_register' kernel test robot
2021-06-18 14:42 ` kernel test robot
2021-06-18 14:56 ` Matthew Wilcox
2021-06-18 14:56 ` Matthew Wilcox
2021-06-21 9:00 ` Rong Chen [this message]
2021-06-21 9:00 ` Rong Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b29ebf9-1ef8-4377-c6c7-4a2186588150@intel.com \
--to=rong.a.chen@intel.com \
--cc=digetx@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=treding@nvidia.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.