From: Roman Gushchin <guro@fb.com> To: Philip Li <philip.li@intel.com> Cc: kernel test robot <lkp@intel.com>, Linus Torvalds <torvalds@linux-foundation.org>, <kbuild-all@lists.01.org>, LKML <linux-kernel@vger.kernel.org>, Bastian Bittorf <bb@npl.de>, Vlastimil Babka <vbabka@suse.cz>, Andrew Morton <akpm@linux-foundation.org>, Linux Memory Management List <linux-mm@kvack.org>, Shakeel Butt <shakeelb@google.com> Subject: Re: [kbuild-all] Re: [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration Date: Fri, 2 Oct 2020 10:55:06 -0700 [thread overview] Message-ID: <20201002175506.GB2954069@carbon.dhcp.thefacebook.com> (raw) In-Reply-To: <20201002053405.GA30771@intel.com> On Fri, Oct 02, 2020 at 01:34:06PM +0800, Philip Li wrote: > On Thu, Oct 01, 2020 at 05:55:59PM -0700, Roman Gushchin wrote: > > On Fri, Oct 02, 2020 at 08:08:40AM +0800, kbuild test robot wrote: > > > Hi Roman, > > > > > > Thank you for the patch! Yet something to improve: > > > > > > [auto build test ERROR on mmotm/master] > > > > It's a bogus error, the patch was applied onto mmotm/master, which doesn't > > contain necessary slab controller patches. > sorry for the wrong report, and thanks for the input, we will check > this to see whether we can find an appropriate base for this case. I wonder if you can look at the "Fixes" tag if the patch contains one? > Meanwhile, you can give a try to use --base option when git format patch, which > helps us to have more clue when looking for base info. Will do. Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Roman Gushchin <guro@fb.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration Date: Fri, 02 Oct 2020 10:55:06 -0700 [thread overview] Message-ID: <20201002175506.GB2954069@carbon.dhcp.thefacebook.com> (raw) In-Reply-To: <20201002053405.GA30771@intel.com> [-- Attachment #1: Type: text/plain, Size: 850 bytes --] On Fri, Oct 02, 2020 at 01:34:06PM +0800, Philip Li wrote: > On Thu, Oct 01, 2020 at 05:55:59PM -0700, Roman Gushchin wrote: > > On Fri, Oct 02, 2020 at 08:08:40AM +0800, kbuild test robot wrote: > > > Hi Roman, > > > > > > Thank you for the patch! Yet something to improve: > > > > > > [auto build test ERROR on mmotm/master] > > > > It's a bogus error, the patch was applied onto mmotm/master, which doesn't > > contain necessary slab controller patches. > sorry for the wrong report, and thanks for the input, we will check > this to see whether we can find an appropriate base for this case. I wonder if you can look at the "Fixes" tag if the patch contains one? > Meanwhile, you can give a try to use --base option when git format patch, which > helps us to have more clue when looking for base info. Will do. Thanks!
next prev parent reply other threads:[~2020-10-02 17:55 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20201001065104.apevlkqrs6nid3r5@hp-nas.internet> 2020-10-01 19:19 ` Linux 5.9-rc7 / VmallocTotal wrongly reported Linus Torvalds 2020-10-01 19:56 ` Roman Gushchin 2020-10-01 19:58 ` Linus Torvalds 2020-10-01 20:39 ` Roman Gushchin 2020-10-02 0:08 ` [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration kernel test robot 2020-10-02 0:08 ` kernel test robot 2020-10-02 0:55 ` Roman Gushchin 2020-10-02 0:55 ` Roman Gushchin 2020-10-02 5:34 ` [kbuild-all] " Philip Li 2020-10-02 5:34 ` Philip Li 2020-10-02 17:55 ` Roman Gushchin [this message] 2020-10-02 17:55 ` Roman Gushchin 2020-10-12 23:05 ` [kbuild-all] " Philip Li 2020-10-12 23:05 ` Philip Li 2020-10-13 0:31 ` [kbuild-all] " Roman Gushchin 2020-10-13 0:31 ` Roman Gushchin 2020-10-02 7:01 ` Linux 5.9-rc7 / VmallocTotal wrongly reported | Patch OK Bastian Bittorf 2020-10-02 17:52 ` Roman Gushchin 2020-10-02 8:51 ` Linux 5.9-rc7 / VmallocTotal wrongly reported Vlastimil Babka 2020-10-02 21:43 ` [PATCH] mm: memcg/slab: fix slab statistics in !SMP configuration kernel test robot 2020-10-02 21:43 ` kernel test robot
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=20201002175506.GB2954069@carbon.dhcp.thefacebook.com \ --to=guro@fb.com \ --cc=akpm@linux-foundation.org \ --cc=bb@npl.de \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=lkp@intel.com \ --cc=philip.li@intel.com \ --cc=shakeelb@google.com \ --cc=torvalds@linux-foundation.org \ --cc=vbabka@suse.cz \ /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: linkBe 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.