From: Dennis Zhou <dennis@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Roman Gushchin <guro@fb.com>, Vlastimil Babka <vbabka@suse.cz>,
Waiman Long <longman@redhat.com>
Subject: Re: linux-next: manual merge of the akpm-current tree with the percpu tree
Date: Thu, 1 Jul 2021 03:31:30 +0000 [thread overview]
Message-ID: <YN03Ej89koHxICKQ@google.com> (raw)
In-Reply-To: <20210701132316.01b6252a@canb.auug.org.au>
Hi Stephen,
On Thu, Jul 01, 2021 at 01:23:16PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 7 Jun 2021 18:33:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the akpm-current tree got a conflict in:
> >
> > mm/memcontrol.c
> >
> > between commit:
> >
> > 0f0cace35fa6 ("mm, memcg: mark cgroup_memory_nosocket, nokmem and noswap as __ro_after_init")
> >
> > from the percpu tree and commits:
> >
> > dfe14954c6e4 ("mm: memcg/slab: don't create kmalloc-cg caches with cgroup.memory=nokmem")
> > 3fd971b13287 ("mm-memcg-slab-create-a-new-set-of-kmalloc-cg-n-caches-v5")
> > 53270d6d0c1f ("mm-memcg-slab-create-a-new-set-of-kmalloc-cg-n-caches-v5-fix")
> >
> > from the akpm-current tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging. You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
> >
> > Andrew, you may want to look at commit
> >
> > 4d5c8aedc8aa ("mm, memcg: introduce mem_cgroup_kmem_disabled()")
> >
> > from the percpu tree.
> >
> > --
> > Cheers,
> > Stephen Rothwell
> >
> > diff --cc mm/memcontrol.c
> > index 3c1641c67122,b9a6db6a7d4f..000000000000
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@@ -80,10 -80,10 +80,10 @@@ struct mem_cgroup *root_mem_cgroup __re
> > DEFINE_PER_CPU(struct mem_cgroup *, int_active_memcg);
> >
> > /* Socket memory accounting disabled? */
> > -static bool cgroup_memory_nosocket;
> > +static bool cgroup_memory_nosocket __ro_after_init;
> >
> > /* Kernel memory accounting disabled? */
> > - static bool cgroup_memory_nokmem __ro_after_init;
> > -bool cgroup_memory_nokmem;
> > ++bool cgroup_memory_nokmem __ro_after_init;
> >
> > /* Whether the swap controller is active */
> > #ifdef CONFIG_MEMCG_SWAP
>
> This is now a conflict between the percpu tree and Linus' tree.
>
Yeah I'm aware. I'm planning on sending my PR tomorrow mentioning it. I
also have an example merge up in percpu#for-5.14-merge for Linus.
Thanks,
Dennis
next prev parent reply other threads:[~2021-07-01 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:33 linux-next: manual merge of the akpm-current tree with the percpu tree Stephen Rothwell
2021-06-08 1:11 ` Roman Gushchin
2021-07-01 3:23 ` Stephen Rothwell
2021-07-01 3:31 ` Dennis Zhou [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-06 2:43 Stephen Rothwell
2016-10-06 2:46 ` Stephen Rothwell
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=YN03Ej89koHxICKQ@google.com \
--to=dennis@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).