From: Mel Gorman <mgorman@suse.de>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Minchan Kim <minchan.kim@gmail.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] mm: vmscan: rework compaction-ready signaling in direct reclaim fix
Date: Fri, 18 Jul 2014 13:50:18 +0100 [thread overview]
Message-ID: <20140718125018.GO10819@suse.de> (raw)
In-Reply-To: <1405344049-19868-2-git-send-email-hannes@cmpxchg.org>
On Mon, Jul 14, 2014 at 09:20:47AM -0400, Johannes Weiner wrote:
> As per Mel, replace out label with breaks from the loop.
>
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Mel Gorman <mgorman@suse.de>
--
Mel Gorman
SUSE Labs
--
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: Mel Gorman <mgorman@suse.de>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Minchan Kim <minchan.kim@gmail.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] mm: vmscan: rework compaction-ready signaling in direct reclaim fix
Date: Fri, 18 Jul 2014 13:50:18 +0100 [thread overview]
Message-ID: <20140718125018.GO10819@suse.de> (raw)
In-Reply-To: <1405344049-19868-2-git-send-email-hannes@cmpxchg.org>
On Mon, Jul 14, 2014 at 09:20:47AM -0400, Johannes Weiner wrote:
> As per Mel, replace out label with breaks from the loop.
>
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Mel Gorman <mgorman@suse.de>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2014-07-18 12:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 13:20 [patch 0/3] mm: vmscan: followup fixes to cleanups in -mm Johannes Weiner
2014-07-14 13:20 ` Johannes Weiner
2014-07-14 13:20 ` [patch 1/3] mm: vmscan: rework compaction-ready signaling in direct reclaim fix Johannes Weiner
2014-07-14 13:20 ` Johannes Weiner
2014-07-14 14:09 ` Rik van Riel
2014-07-14 14:09 ` Rik van Riel
2014-07-18 12:50 ` Mel Gorman [this message]
2014-07-18 12:50 ` Mel Gorman
2014-07-14 13:20 ` [patch 2/3] mm: vmscan: remove all_unreclaimable() fix Johannes Weiner
2014-07-14 13:20 ` Johannes Weiner
2014-07-14 14:10 ` Rik van Riel
2014-07-14 14:10 ` Rik van Riel
2014-07-16 9:40 ` Michal Hocko
2014-07-16 9:40 ` Michal Hocko
2014-07-18 12:51 ` Mel Gorman
2014-07-18 12:51 ` Mel Gorman
2014-07-14 13:20 ` [patch 3/3] mm: vmscan: clean up struct scan_control Johannes Weiner
2014-07-14 13:20 ` Johannes Weiner
2014-07-14 19:46 ` Hugh Dickins
2014-07-14 19:46 ` Hugh Dickins
2014-07-17 13:26 ` Johannes Weiner
2014-07-17 13:26 ` Johannes Weiner
2014-07-17 13:57 ` Michal Hocko
2014-07-17 13:57 ` Michal Hocko
2014-07-17 23:00 ` Hugh Dickins
2014-07-17 23:00 ` Hugh Dickins
2014-07-18 12:53 ` Mel Gorman
2014-07-18 12:53 ` Mel Gorman
2014-07-14 19:56 ` Andrew Morton
2014-07-14 19:56 ` Andrew Morton
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=20140718125018.GO10819@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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 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.