From: Lord Glauber Costa of Sealand <glommer@parallels.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] memcg: stop warning on memcg_propagate_kmem
Date: Mon, 4 Feb 2013 11:36:25 +0400 [thread overview]
Message-ID: <510F64F9.2050706@parallels.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1302032023280.4611@eggly.anvils>
On 02/04/2013 08:29 AM, Hugh Dickins wrote:
> Whilst I run the risk of a flogging for disloyalty to the Lord of Sealand,
> I do have CONFIG_MEMCG=y CONFIG_MEMCG_KMEM not set, and grow tired of the
> "mm/memcontrol.c:4972:12: warning: `memcg_propagate_kmem' defined but not
> used [-Wunused-function]" seen in 3.8-rc: move the #ifdef outwards.
>
Thanks my dear Hugh,
This is no disloyalty at all, and your braveness is indeed much appreciated.
My bad for letting that one slip
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Lord Glauber Costa of Sealand <glommer@parallels.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [PATCH] memcg: stop warning on memcg_propagate_kmem
Date: Mon, 4 Feb 2013 11:36:25 +0400 [thread overview]
Message-ID: <510F64F9.2050706@parallels.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1302032023280.4611@eggly.anvils>
On 02/04/2013 08:29 AM, Hugh Dickins wrote:
> Whilst I run the risk of a flogging for disloyalty to the Lord of Sealand,
> I do have CONFIG_MEMCG=y CONFIG_MEMCG_KMEM not set, and grow tired of the
> "mm/memcontrol.c:4972:12: warning: `memcg_propagate_kmem' defined but not
> used [-Wunused-function]" seen in 3.8-rc: move the #ifdef outwards.
>
Thanks my dear Hugh,
This is no disloyalty at all, and your braveness is indeed much appreciated.
My bad for letting that one slip
next prev parent reply other threads:[~2013-02-04 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 4:29 [PATCH] memcg: stop warning on memcg_propagate_kmem Hugh Dickins
2013-02-04 4:29 ` Hugh Dickins
2013-02-04 7:36 ` Lord Glauber Costa of Sealand [this message]
2013-02-04 7:36 ` Lord Glauber Costa of Sealand
2013-02-04 7:57 ` Michal Hocko
2013-02-04 7:57 ` Michal Hocko
2013-02-04 8:04 ` Lord Glauber Costa of Sealand
2013-02-04 8:04 ` Lord Glauber Costa of Sealand
2013-02-04 8:36 ` Michal Hocko
2013-02-04 8:36 ` Michal Hocko
2013-02-04 8:40 ` Lord Glauber Costa of Sealand
2013-02-04 8:40 ` Lord Glauber Costa of Sealand
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=510F64F9.2050706@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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 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.