From: Johannes Weiner <jweiner@redhat.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
Michal Hocko <mhocko@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
abrestic@google.com
Subject: Re: [PATCH v3] memcg: add memory.vmscan_stat
Date: Tue, 9 Aug 2011 10:01:59 +0200 [thread overview]
Message-ID: <20110809080159.GA32015@redhat.com> (raw)
In-Reply-To: <20110809083345.46cbc8de.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Aug 09, 2011 at 08:33:45AM +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 8 Aug 2011 14:43:33 +0200
> Johannes Weiner <jweiner@redhat.com> wrote:
> > On a non-technical note: as Ying Han and I were the other two people
> > working on reclaim and statistics, it really irks me that neither of
> > us were CCd on this. Especially on such a controversial change.
>
> I always drop CC if no reply/review comes.
There is always the possibility that a single mail in an otherwise
unrelated patch series is overlooked (especially while on vacation ;).
Getting CCd on revisions and -mm inclusion is a really nice reminder.
Unless there is a really good reason not to (is there ever?), could
you please keep CCs?
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <jweiner@redhat.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
Michal Hocko <mhocko@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
abrestic@google.com
Subject: Re: [PATCH v3] memcg: add memory.vmscan_stat
Date: Tue, 9 Aug 2011 10:01:59 +0200 [thread overview]
Message-ID: <20110809080159.GA32015@redhat.com> (raw)
In-Reply-To: <20110809083345.46cbc8de.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Aug 09, 2011 at 08:33:45AM +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 8 Aug 2011 14:43:33 +0200
> Johannes Weiner <jweiner@redhat.com> wrote:
> > On a non-technical note: as Ying Han and I were the other two people
> > working on reclaim and statistics, it really irks me that neither of
> > us were CCd on this. Especially on such a controversial change.
>
> I always drop CC if no reply/review comes.
There is always the possibility that a single mail in an otherwise
unrelated patch series is overlooked (especially while on vacation ;).
Getting CCd on revisions and -mm inclusion is a really nice reminder.
Unless there is a really good reason not to (is there ever?), could
you please keep CCs?
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-09 8:02 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 8:15 [PATCH v3] memcg: add memory.vmscan_stat KAMEZAWA Hiroyuki
2011-07-22 8:15 ` KAMEZAWA Hiroyuki
2011-08-08 12:43 ` Johannes Weiner
2011-08-08 12:43 ` Johannes Weiner
2011-08-08 23:33 ` KAMEZAWA Hiroyuki
2011-08-08 23:33 ` KAMEZAWA Hiroyuki
2011-08-09 8:01 ` Johannes Weiner [this message]
2011-08-09 8:01 ` Johannes Weiner
2011-08-09 8:01 ` KAMEZAWA Hiroyuki
2011-08-09 8:01 ` KAMEZAWA Hiroyuki
2011-08-13 1:04 ` Ying Han
2011-08-13 1:04 ` Ying Han
2011-08-29 15:51 ` [patch] Revert "memcg: add memory.vmscan_stat" Johannes Weiner
2011-08-29 15:51 ` Johannes Weiner
2011-08-30 1:12 ` KAMEZAWA Hiroyuki
2011-08-30 1:12 ` KAMEZAWA Hiroyuki
2011-08-30 7:04 ` Johannes Weiner
2011-08-30 7:04 ` Johannes Weiner
2011-08-30 7:20 ` KAMEZAWA Hiroyuki
2011-08-30 7:20 ` KAMEZAWA Hiroyuki
2011-08-30 7:35 ` KAMEZAWA Hiroyuki
2011-08-30 7:35 ` KAMEZAWA Hiroyuki
2011-08-30 8:42 ` Johannes Weiner
2011-08-30 8:42 ` Johannes Weiner
2011-08-30 8:56 ` KAMEZAWA Hiroyuki
2011-08-30 8:56 ` KAMEZAWA Hiroyuki
2011-08-30 10:17 ` Johannes Weiner
2011-08-30 10:17 ` Johannes Weiner
2011-08-30 10:34 ` KAMEZAWA Hiroyuki
2011-08-30 10:34 ` KAMEZAWA Hiroyuki
2011-08-30 11:03 ` Johannes Weiner
2011-08-30 11:03 ` Johannes Weiner
2011-08-30 23:38 ` KAMEZAWA Hiroyuki
2011-08-30 23:38 ` KAMEZAWA Hiroyuki
2011-08-30 10:38 ` KAMEZAWA Hiroyuki
2011-08-30 10:38 ` KAMEZAWA Hiroyuki
2011-08-30 11:32 ` Johannes Weiner
2011-08-30 11:32 ` Johannes Weiner
2011-08-30 23:29 ` KAMEZAWA Hiroyuki
2011-08-30 23:29 ` KAMEZAWA Hiroyuki
2011-08-31 6:23 ` Johannes Weiner
2011-08-31 6:23 ` Johannes Weiner
2011-08-31 6:30 ` KAMEZAWA Hiroyuki
2011-08-31 6:30 ` KAMEZAWA Hiroyuki
2011-08-31 8:33 ` Johannes Weiner
2011-08-31 8:33 ` Johannes Weiner
2011-09-01 6:05 ` Ying Han
2011-09-01 6:05 ` Ying Han
2011-09-01 6:40 ` Johannes Weiner
2011-09-01 6:40 ` Johannes Weiner
2011-09-01 7:04 ` Ying Han
2011-09-01 7:04 ` Ying Han
2011-09-01 8:27 ` Johannes Weiner
2011-09-01 8:27 ` Johannes Weiner
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=20110809080159.GA32015@redhat.com \
--to=jweiner@redhat.com \
--cc=abrestic@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=nishimura@mxp.nes.nec.co.jp \
/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.