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@xxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx/
Do you want us to adjust the polices?
Best Regards,
Rong Chen
