From: caiqian@redhat.com
To: Michel Lespinasse <walken@google.com>
Cc: " \"linux-mm\"; \"Rik van Riel\" <riel@redhat.com>; \"Wu
Fengguang\" <fengguang.wu@intel.com>; \"H. Peter Anvin\"
<hpa@zytor.com>; \"Linus Torvalds" <linux-mm@kvack.org>
Subject: Re: oom is broken in mmotm 2010-11-09-15-31 tree?
Date: Wed, 1 Dec 2010 22:11:12 -0500 (EST) [thread overview]
Message-ID: <1607175419.1020111291259472474.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1415319777.1020071291259410217.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
> Things are known to be broken between
> d065bd810b6deb67d4897a14bfe21f8eb526ba99 and
> d88c0922fa0e2c021a028b310a641126c6d4b7dc. CAI, do you have that in
> your tree ? Also, can you test at
> d065bd810b6deb67d4897a14bfe21f8eb526ba99 with
> d88c0922fa0e2c021a028b310a641126c6d4b7dc cherry-picked on ?
Hi Michel, the mmotm tree did not include d88c0922fa0e2c021a028b310a641126c6d4b7dc.
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2010-12-02 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1415319777.1020071291259410217.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-12-02 3:11 ` caiqian [this message]
[not found] <1043135380.1026761291266384009.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-12-02 5:07 ` oom is broken in mmotm 2010-11-09-15-31 tree? caiqian
2010-12-02 5:12 ` Linus Torvalds
2010-12-02 6:40 ` CAI Qian
2010-12-02 6:48 ` CAI Qian
2010-12-01 2:44 CAI Qian
2010-12-01 19:29 ` CAI Qian
2010-12-01 20:15 ` Linus Torvalds
2010-12-01 21:40 ` Michel Lespinasse
2010-12-02 4:26 ` CAI Qian
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=1607175419.1020111291259472474.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=caiqian@redhat.com \
--cc=linux-mm@kvack.org \
--cc=walken@google.com \
/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).