diff for duplicates of <20211101171533.GA527894@bhelgaas> diff --git a/a/1.txt b/N1/1.txt index aeb4f5a..6f0a1cd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -8,9 +8,9 @@ think this is a problem. For example here are Xuesong's original patch, the patch in patchwork, and the 0-day bot report: - https://lore.kernel.org/all/20211027081312.53682-1-xuesong.chen@linux.alibaba.com/ - https://patchwork.kernel.org/project/linux-pci/patch/20211027081312.53682-1-xuesong.chen@linux.alibaba.com/ - https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/QISVC5TJIHTEMAPX7T7YXOZEDS5CBURY/ + https://lore.kernel.org/all/20211027081312.53682-1-xuesong.chen(a)linux.alibaba.com/ + https://patchwork.kernel.org/project/linux-pci/patch/20211027081312.53682-1-xuesong.chen(a)linux.alibaba.com/ + https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org/thread/QISVC5TJIHTEMAPX7T7YXOZEDS5CBURY/ Neither the lore link nor the patchwork have any indication that the 0-day bot found a problem. @@ -18,15 +18,15 @@ Neither the lore link nor the patchwork have any indication that the It looks like the 0-day bot sent the report to all the individual recipients from the original patch, but it ADDED these recipients: - llvm@lists.linux.dev - kbuild-all@lists.01.org + llvm(a)lists.linux.dev + kbuild-all(a)lists.01.org and REMOVED these: - linux-pci@vger.kernel.org - linux-acpi@vger.kernel.org - linux-arm-kernel@lists.infradead.org - linux-kernel@vger.kernel.org + linux-pci(a)vger.kernel.org + linux-acpi(a)vger.kernel.org + linux-arm-kernel(a)lists.infradead.org + linux-kernel(a)vger.kernel.org Gmail filed Xuesong's original patch and the 0-day report as spam. That's a problem on my end, but the bigger problem is that I work from @@ -42,7 +42,7 @@ different? I added linux-pci to cc, but since the 0-day report didn't go to the list, I don't think this message will be threaded correctly on lore. It should be part of -https://lore.kernel.org/all/20211027081035.53370-1-xuesong.chen@linux.alibaba.com/ +https://lore.kernel.org/all/20211027081035.53370-1-xuesong.chen(a)linux.alibaba.com/ On Thu, Oct 28, 2021 at 06:46:16AM +0800, kernel test robot wrote: > Hi Xuesong, @@ -82,4 +82,4 @@ On Thu, Oct 28, 2021 at 06:46:16AM +0800, kernel test robot wrote: > > --- > 0-DAY CI Kernel Test Service, Intel Corporation -> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org +> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org diff --git a/a/content_digest b/N1/content_digest index d830218..66843d2 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,9 @@ "ref\0202110280656.2MEz43OU-lkp@intel.com\0" "From\0Bjorn Helgaas <helgaas@kernel.org>\0" "Subject\0Re: [PATCH v4 3/4] ACPI: APEI: Reserve the MCFG address for quirk ECAM implementation\0" - "Date\0Mon, 1 Nov 2021 12:15:33 -0500\0" - "To\0kernel test robot <lkp@intel.com>" - " kbuild-all-owner@lists.01.org\0" - "Cc\0Xuesong Chen <xuesong.chen@linux.alibaba.com>" - kbuild-all@lists.01.org - linux-pci@vger.kernel.org - " Konstantin Ryabitsev <konstantin@linuxfoundation.org>\0" - "\00:1\0" + "Date\0Mon, 01 Nov 2021 12:15:33 -0500\0" + "To\0kbuild-all@lists.01.org\0" + "\01:1\0" "b\0" "[+cc linux-pci, Konstantin, since you're thinking about this area, too]\n" "\n" @@ -20,9 +15,9 @@ "For example here are Xuesong's original patch, the patch in patchwork,\n" "and the 0-day bot report:\n" "\n" - " https://lore.kernel.org/all/20211027081312.53682-1-xuesong.chen@linux.alibaba.com/\n" - " https://patchwork.kernel.org/project/linux-pci/patch/20211027081312.53682-1-xuesong.chen@linux.alibaba.com/\n" - " https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/QISVC5TJIHTEMAPX7T7YXOZEDS5CBURY/\n" + " https://lore.kernel.org/all/20211027081312.53682-1-xuesong.chen(a)linux.alibaba.com/\n" + " https://patchwork.kernel.org/project/linux-pci/patch/20211027081312.53682-1-xuesong.chen(a)linux.alibaba.com/\n" + " https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org/thread/QISVC5TJIHTEMAPX7T7YXOZEDS5CBURY/\n" "\n" "Neither the lore link nor the patchwork have any indication that the\n" "0-day bot found a problem.\n" @@ -30,15 +25,15 @@ "It looks like the 0-day bot sent the report to all the individual\n" "recipients from the original patch, but it ADDED these recipients:\n" "\n" - " llvm@lists.linux.dev\n" - " kbuild-all@lists.01.org\n" + " llvm(a)lists.linux.dev\n" + " kbuild-all(a)lists.01.org\n" "\n" "and REMOVED these:\n" "\n" - " linux-pci@vger.kernel.org\n" - " linux-acpi@vger.kernel.org\n" - " linux-arm-kernel@lists.infradead.org\n" - " linux-kernel@vger.kernel.org\n" + " linux-pci(a)vger.kernel.org\n" + " linux-acpi(a)vger.kernel.org\n" + " linux-arm-kernel(a)lists.infradead.org\n" + " linux-kernel(a)vger.kernel.org\n" "\n" "Gmail filed Xuesong's original patch and the 0-day report as spam.\n" "That's a problem on my end, but the bigger problem is that I work from\n" @@ -54,7 +49,7 @@ "I added linux-pci to cc, but since the 0-day report didn't go to the\n" "list, I don't think this message will be threaded correctly on lore.\n" "It should be part of\n" - "https://lore.kernel.org/all/20211027081035.53370-1-xuesong.chen@linux.alibaba.com/\n" + "https://lore.kernel.org/all/20211027081035.53370-1-xuesong.chen(a)linux.alibaba.com/\n" "\n" "On Thu, Oct 28, 2021 at 06:46:16AM +0800, kernel test robot wrote:\n" "> Hi Xuesong,\n" @@ -94,6 +89,6 @@ "> \n" "> ---\n" "> 0-DAY CI Kernel Test Service, Intel Corporation\n" - > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org + > https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org -920589df48117eb2d8cfb2d065691986af52182af5218c9eb21d4b57637185ad +1a22f491fd2b9b018b5c0d44d7067b7e410a1333156352ac62230c65108c3e42
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.